Update `BaseOperator` imports for Airflow 3.0 compatibility

[kaxil]

We need community help to migrate all provider packages to use the new Task SDK BaseOperator import for Airflow 3.0 compatibility while maintaining backward compatibility with Airflow 2.x.

Background

With Airflow 3.0, the BaseOperator has moved to the Task SDK (airflow.sdk). All provider packages need to be updated to use version-compatible imports to work with both Airflow 2.x and 3.x versions.

Migration Tasks

Use #52366 & #52292 as reference.

Each provider needs these updates:

1. Create/update version_compat.py with standardized version compatibility pattern
2. Update imports in all operator, sensor, hook, and link files
3. Fix BaseOperatorLink.persist methods that cause AttributeError with SDK BaseOperator
4. Update test patterns to use dag_maker.run_ti() instead of deprecated patterns

Provider Status Checklist

• airbyte - @kevinhongzl - Provider Migration: Update airbyte provider for Airflow 3.0 compatibility #52418
• alibaba - @kaxil - Replace models.BaseOperator to Task SDK one for Alibaba & Airbyte #52335
• amazon - @kaxil - Replace models.BaseOperator to Task SDK one for Amazon Provider #52667
• apache/beam - @kgw7401 - Provider Migration: Update beam for Airflow 3.0 compatibility #52607
• apache/cassandra - @Nataneljpwd - Provider Migration: Update cassandra for Airflow 3.0 compatibility #52623
• apache/drill - No base operator
• apache/druid - @sjyangkevin - Provider Migration: Update Apache Druid for Airflow 3.0 compatibility #52498
• apache/flink - @sjyangkevin - Provider Migration: Update Apache Flink for Airflow 3.0 compatibility #52504
• apache/hdfs - @bdsoha - Provider Migration: Replace models.BaseOperator to Task SDK for apache/hdfs #52505
• apache/hive - @bdsoha - Provider Migration: Replace models.BaseOperator to Task SDK for apache/hive #52453
• apache/iceberg - no base operator
• apache/impala - @bdsoha - Provider Migration: Replace models.BaseOperator to Task SDK for apache/impala #52455
• apache/kafka - @sjyangkevin - Provider Migration: Update Apache Kafka for Airflow 3.0 compatibility #52503
• apache/kylin - @fweilun - Provider Migration: Update Apache Kylin for Airflow 3.0 compatibility #52572
• apache/livy - @bdsoha Provider Migration: Replace models.BaseOperator to Task SDK for apache/livy #52499
• apache/pig - @kaxil - Replace models.BaseOperator to Task SDK one for Apache Pig #52375
• apache/pinot - no base operator
• apache/spark - @kgw7401 - Provider Migration: Update spark for Airflow 3.0 compatibility #52448
• apache/tinkerpop - @ahmadtfarhan - Replace models.BaseOperator to Task SDK one for Apache TinkerPop #52400
• apprise - no base operator
• arangodb - @kaxil - Replace models.BaseOperator to Task SDK one for Asana & Arangodb #52374
• asana - @kaxil - Replace models.BaseOperator to Task SDK one for Asana & Arangodb #52374
• atlassian/jira - @kaxil - Replace models.BaseOperator to Task SDK one for Atlassian #52376
• celery - no base operator
• cloudant - no base operator
• cncf/kubernetes - @kaxil - Update Kubernetes provider for Airflow 3.0 compatibility #52664
• cohere - @sjyangkevin - Provider Migration: Update Cohere for Airflow 3.0 compatibility #52379
• common/compat - @kaxil - Replace models.BaseOperator to Task SDK one for Common Providers #52443
• common/io - @kaxil - Replace models.BaseOperator to Task SDK one for Common Providers #52443
• common/messaging - No BaseOperator
• common/sql - @kaxil - Replace models.BaseOperator to Task SDK one for Common Providers #52443
• databricks - @kaxil - Replace models.BaseOperator to Task SDK one for DBT & Databricks #52377
• datadog - @kevinhongzl Provider Migration: Replace BaseSensorOperator to Task SDK for datadog #52583
• dbt/cloud - @kaxil - Replace models.BaseOperator to Task SDK one for DBT & Databricks #52377
• dingding - @kevinhongzl Provider Migration: Replace BaseOperator to Task SDK for dingding #52577
• discord - No BaseOperator
• docker - @hardeybisey - Provider Migration: Update docker for Airflow 3.0 compatibility #52465
• edge3 - not using BaseOperator
• elasticsearch - no base operator
• exasol - no base operator
• fab - no base operator
• facebook - no base operator
• ftp - @sunank200 - Replace models.BaseOperator to Task SDK one for ftp #52338
• git - no base operator
• github - @kevinhongzl - Provider Migration: Update github provider for Airflow 3.0 compatibility #52415
• google - @kaxil - Replace models.BaseOperator to Task SDK one for Google Provider #52366
• grpc - @karenbraganz - Update grpc BaseOperator imports for Airflow 3.0 compatibility #52603
• hashicorp - no base operator
• http - @bdsoha @kaxil - Provider Migration: Replace models.BaseOperator to Task SDK for apache/http #52506 | Provider Migration: Replace BaseOperator to Task SDK for apache/http #52528
• imap - no base operator
• influxdb - @karenbraganz - Update influxdb BaseOperator imports for Airflow 3.0 compatibility #52602
• jdbc - no base operator
• jenkins - @gopidesupavan - Update Jenkins for Airflow 3.0 compatibility #52510
• keycloak - no base operator
• microsoft/azure - @kyungjunleeme - Provider Migration: Update azure for Airflow 3.0 compatibility #52618
• microsoft/mssql - no base operator
• microsoft/psrp - @sunank200 - Replace airflow.models.baseoperator to airflow.sdk for Microsoft PSRP #52654
• microsoft/winrm - @sunank200 - Replace airflow.models.baseoperator to airflow.sdk for Microsoft Winrm #52657
• mongo - @jroachgolf84 - Replace models.BaseSensorOperator to Task SDK one for Mongo #52566
• mysql - @kgw7401 - Provider Migration: Update mysql for Airflow 3.0 compatibility #52500
• neo4j - @kyungjunleeme Provider Migration: Update neo4j for Airflow 3.0 compatibility #52610
• odbc - no base operator
• openai - @kaxil - Provider Migration: Replace BaseOperator to Task SDK for OpenAI #52561
• openfaas - no base operator
• openlineage - no base operator
• opensearch - @kyungjunleeme - Provider Migration: Update opensearch for Airflow 3.0 compatibility #52609
• opsgenie - @jroachgolf84 - Replace models.BaseOperator to Task SDK one for OpsGenie #52564
• oracle - @sjyangkevin - Provider Migration: Update Oracle for Airflow 3.0 compatibility #52382
• pagerduty - no base operator
• papermill - @kaxil - Provider Migration: Replace BaseOperator to Task SDK for Papermill #52565
• pgvector - Does not directly use BaseOperator
• pinecone - @kaxil - Provider Migration: Replace BaseOperator to Task SDK for Pinecone #52563
• postgres - @kgw7401 - no base operator
• presto - @kyungjunleeme Provider Migration: Update presto for Airflow 3.0 compatibility #52608
• qdrant - @karenbraganz - Update BaseOperator and BaseSensorOperator imports for Airflow 3.0 compatibility in qdrant provider #52600
• redis - @karenbraganz - Update BaseOperator and BaseSensorOperator imports for Airflow 3.0 compatibility in redis provider #52597
• salesforce - @kevinhongzl - Provider Migration: Replace BaseOperator to Task SDK for salesforce #52587
• samba - @kevinhongzl - Provider Migration: Replace BaseOperator to Task SDK for samba #52588
• segment - @gopidesupavan - Provider Migration: Replace BaseOperator to Task SDK for segment #52579
• sendgrid - no base operator
• sftp - @jroachgolf84 - Replace models.BaseOperator to Task SDK one for SFTP #52435
• singularity - @kevinhongzl - Provider Migration: Replace BaseOperator to Task SDK for singularity #52590
• slack - @vatsrahul1001 - Replace models.BaseOperator to Task SDK one for Slack Provider #52347
• smtp - @gyli - Provider Migration: Replace models.BaseOperator to Task SDK for smtp #52596
• snowflake - @rawwar - Provider Migration: Update Snowflake provider for Airflow 3.0 compatibility  #52629
• sqlite - no base operator
• ssh - @kaxil - Provider Migration: Replace BaseOperator to Task SDK for ssh #52558
• standard - @kaxil - Replace models.BaseOperator to Task SDK one for Standard Provider #52292
• tableau - @jroachgolf84 - Replace models.BaseOperator to Task SDK one for Tableau, Telegram, and Teradata #52642
• telegram - @jroachgolf84 - Replace models.BaseOperator to Task SDK one for Tableau, Telegram, and Teradata #52642
• teradata - @jroachgolf84 - Replace models.BaseOperator to Task SDK one for Tableau, Telegram, and Teradata #52642
• trino - @kyungjunleeme Provider Migration: Update trino for Airflow 3.0 compatibility  #52383
• vertica - no base operator
• weaviate - @sjyangkevin Provider Migration: Update Weaviate for Airflow 3.0 compatibility #52381
• yandex - @kevinhongzl - Provider Migration: Update yandex provider for Airflow 3.0 compatibility  #52422
• ydb - no use of BaseOperator
• zendesk - no use of BaseOperator

Implementation Guide

If using AI Agents, refer to #52378 (comment)

Step 1: Create version_compat.py

# In providers/{provider_name}/src/airflow/providers/{provider_name}/version_compat.py
from __future__ import annotations

def get_base_airflow_version_tuple() -> tuple[int, int, int]:
    from packaging.version import Version
    from airflow import __version__
    airflow_version = Version(__version__)
    return airflow_version.major, airflow_version.minor, airflow_version.micro

AIRFLOW_V_3_0_PLUS = get_base_airflow_version_tuple() >= (3, 0, 0)

if AIRFLOW_V_3_0_PLUS:
    from airflow.sdk import BaseOperator
else:
    from airflow.models import BaseOperator

__all__ = ["AIRFLOW_V_3_0_PLUS", "BaseOperator"]

Step 2: Update imports

Replace:

  from airflow.models.baseoperator import BaseOperator

With:

  from airflow.providers.{provider_name}.version_compat import BaseOperator

Step 3: Fix BaseOperatorLink.persist methods

Replace:

  def persist(context: Context, task_instance: BaseOperator, url: str):
      task_instance.xcom_push(key="link_key", value=url)

With:

  def persist(context: Context, url: str):
      context["task_instance"].xcom_push(key="link_key", value=url)

Step 4: Update test patterns

Replace operator.run() with dag_maker.run_ti(task_id, dr). Use #52366 & #52292 as reference.

Test your changes:

  # Run provider tests
  breeze testing providers-tests --test-type "Providers[{provider_name}]"

How to Contribute

1. Pick an unchecked provider from the list above
2. Comment on this issue to claim it (prevents duplicate work)
3. Follow the implementation guide
4. Submit a PR with title: Provider Migration: Update {provider_name} for Airflow 3.0 compatibility
5. Check off the completed provider in this issue

[kyungjunleeme]

@kaxil

Would it be okay if I pick the providers I’d like to work on and start from there?
If so, I’d be happy to work on dbt, opensearch, presto, trino, and neo4j.

[sjyangkevin]

I could help with cohere and weaviate.

[1fanwang]

Would love to contribute to cncf/kubernetes,thanks!

[sjyangkevin]

I am wondering for providers such as iceberg, and pinot, there is only hook for these providers. Should we also create a version_compat.py for these providers even though no changes are required for the hook?
https://github.com/apache/airflow/blob/main/providers/apache/pinot/src/airflow/providers/apache/pinot/hooks/pinot.py
https://github.com/apache/airflow/blob/main/providers/apache/iceberg/src/airflow/providers/apache/iceberg/hooks/iceberg.py

I can also take

Provider Migration: Update [druid,iceberg,pinot,kafka,flink] for Airflow 3.0 compatibility

• apache/druid
• apache/iceberg
• apache/pinot
• apache/kafka
• apache/flink

Provider Migration: Update Oracle for Airflow 3.0 compatibility

• oracle

[kgw7401]

i could help with apache/beam, apache/spark, postgres

[kevinhongzl]

I'll start with github!

[kaxil]

I am wondering for providers such as iceberg, and pinot, there is only hook for these providers.

If there are no operators, we can skip those providers for now.

[kaxil]

More details, especially if you plan to use AI for this work (you can feed this as a prompt):

---

⚠️ CRITICAL WARNING ⚠️

DO NOT MODIFY THE TASK SDK (airflow.sdk)

• Never add methods to airflow.sdk.BaseOperator
• Never modify any components in airflow.sdk
• Use version compatibility patterns to work around SDK limitations
• If the entire provider directory does not import BaseOperator, no changes should be made to the Provider.

Summary

Update all provider packages to use the new Task SDK BaseOperator import for Airflow 3.0 compatibility while maintaining backward compatibility with Airflow 2.x. This involves updating import statements, fixing test patterns, and resolving xcom_push method signature issues.

Migration Strategy

1. Version Compatibility Pattern

For ALL providers, use this centralized version compatibility approach:

# In providers/{provider_name}/src/airflow/providers/{provider_name}/version_compat.py
from __future__ import annotations

def get_base_airflow_version_tuple() -> tuple[int, int, int]:
    from packaging.version import Version
    from airflow import __version__
    airflow_version = Version(__version__)
    return airflow_version.major, airflow_version.minor, airflow_version.micro

# Choose the right version flag based on your provider's needs:
# - Use AIRFLOW_V_3_0_PLUS for most providers (BaseOperator, BaseSensorOperator, etc.)
# - Use AIRFLOW_V_3_1_PLUS only if you have decorators with xcom_push issues
AIRFLOW_V_3_0_PLUS = get_base_airflow_version_tuple() >= (3, 0, 0)

if AIRFLOW_V_3_0_PLUS:
    from airflow.sdk import BaseOperator  # Use BaseOperator for most providers
    # Only include other components if your provider uses them:
    # from airflow.sdk import BaseOperatorLink, BaseSensorOperator
    # from airflow.sdk.execution_time.xcom import XCom
else:
    from airflow.models import BaseOperator
    # Only include other components if your provider uses them:
    # from airflow.models import BaseOperatorLink, XCom
    # from airflow.sensors.base import BaseSensorOperator

__all__ = [
    "AIRFLOW_V_3_0_PLUS",
    "BaseOperator",
    # Only include what your provider actually uses:
    # "BaseSensorOperator",
    # "BaseOperatorLink", 
    # "XCom",
]

IMPORTANT: The above is a template showing all possible imports. Each provider should:

1. Always include: AIRFLOW_V_3_1_PLUS and BaseOperator (every provider needs these)
2. Only include if used: Remove any SDK components your provider doesn't actually use
3. Keep it minimal: Only import what you need to avoid unnecessary dependencies

Example for a simple provider (like most providers with only operators, no decorators):

# Minimal version_compat.py for providers with only operators
from __future__ import annotations

def get_base_airflow_version_tuple() -> tuple[int, int, int]:
    from packaging.version import Version
    from airflow import __version__
    airflow_version = Version(__version__)
    return airflow_version.major, airflow_version.minor, airflow_version.micro

AIRFLOW_V_3_0_PLUS = get_base_airflow_version_tuple() >= (3, 0, 0)

if AIRFLOW_V_3_0_PLUS:
    from airflow.sdk import BaseOperator
else:
    from airflow.models import BaseOperator

__all__ = [
    "AIRFLOW_V_3_0_PLUS",
    "BaseOperator",
]

Example for providers with decorators that have xcom_push issues (use AIRFLOW_V_3_1_PLUS):

# For providers with decorators that trigger xcom_push bugs in 3.0.x
from __future__ import annotations

def get_base_airflow_version_tuple() -> tuple[int, int, int]:
    from packaging.version import Version
    from airflow import __version__
    airflow_version = Version(__version__)
    return airflow_version.major, airflow_version.minor, airflow_version.micro

AIRFLOW_V_3_1_PLUS = get_base_airflow_version_tuple() >= (3, 1, 0)

if AIRFLOW_V_3_1_PLUS:
    from airflow.sdk import BaseOperator
else:
    from airflow.models import BaseOperator

__all__ = [
    "AIRFLOW_V_3_1_PLUS",
    "BaseOperator",
]

Key Decision Rules:

• Use AIRFLOW_V_3_0_PLUS for BaseOperator imports in most providers
• Use AIRFLOW_V_3_1_PLUS for BaseOperator ONLY if your provider has decorators that use xcom_push (avoids SDK BaseOperator xcom_push bug in Airflow 3.0.x)
• Use AIRFLOW_V_3_0_PLUS for other SDK components (BaseOperatorLink, BaseSensorOperator, XCom)
• Use from tests_common.test_utils.version_compat import AIRFLOW_V_3_0_PLUS for the code in "tests". (Verify it by running check-airflow-v-imports-in-tests pre-commit hook.)

2. Update All Provider Files

Replace direct imports in all operator, sensor, hook, and link files:

# OLD PATTERN
from airflow.models.baseoperator import BaseOperator

# NEW PATTERN
from airflow.providers.{provider_name}.version_compat import BaseOperator

For TYPE_CHECKING blocks, maintain compatibility:

if TYPE_CHECKING:
    from airflow.providers.{provider_name}.version_compat import AIRFLOW_V_3_1_PLUS
    if AIRFLOW_V_3_1_PLUS:
        from airflow.sdk import BaseOperator
    else:
        from airflow.models import BaseOperator

3. Fix BaseOperatorLink.persist Method Signatures

Critical Issue: Many providers have BaseOperatorLink.persist methods that unnecessarily pass task_instance: BaseOperator parameter and call task_instance.xcom_push(), causing AttributeError with SDK BaseOperator.

Fix Pattern:

# OLD PATTERN - causes AttributeError
@staticmethod
def persist(
    context: Context,
    task_instance: BaseOperator,  # ❌ Remove this parameter
    log_view_url: str,
):
    task_instance.xcom_push(key="link_key", value=log_view_url)  # ❌ Fails

# NEW PATTERN - works universally
@staticmethod  
def persist(
    context: Context,
    log_view_url: str,
):
    context["task_instance"].xcom_push(key="link_key", value=log_view_url)  # ✅ Works

Common xcom_push Signature Errors:

# WRONG - extra context parameter
context["task_instance"].xcom_push(context, key="key", value="value")

# CORRECT - no context parameter
context["task_instance"].xcom_push(key="key", value="value")

4. Test Pattern Updates

Mock Context Type Issues:

# OLD PATTERN - causes mypy errors
mock_context = {"ti": mock_ti}
result = task.execute(context=mock_context)  # ❌ Type error

# NEW PATTERN - add type ignore for test simplicity
mock_context = {"ti": mock_ti, "task_instance": mock_ti}
result = task.execute(context=mock_context)  # type: ignore[arg-type]  # ✅ Works

Decorator Test Patterns:

# OLD PATTERN - fails in Airflow 3.0
@task.virtualenv
def f():
    return "hello"

ret = f()
ret.operator.run(start_date=DEFAULT_DATE, end_date=DEFAULT_DATE)  # ❌ AttributeError

# NEW PATTERN - use dag_maker.run_ti()
@task.virtualenv  
def f():
    return "hello"

ret = f()
dr = dag_maker.create_dagrun()
dag_maker.run_ti("f", dr)  # ✅ Works - use function name directly

Critical DAG Creation Pattern:

# WRONG - causes task instance issues
dr = self.create_dag_run()
dag_maker.run_ti("task_id", dr)  # ❌ May fail

# CORRECT - ensures proper task instance creation
dr = self.dag_maker.create_dagrun() 
dag_maker.run_ti("task_id", dr)  # ✅ Works correctly

Automation Checklist

For agentic AI to automate this migration:

Phase 1: Version Compatibility Setup

1. ✅ Create/update version_compat.py in each provider's root package.
2. ✅ Use the standardized version compatibility pattern above
3. ✅ Always include BaseOperator (required for all providers)
4. ✅ Choose the right version flag: Use AIRFLOW_V_3_0_PLUS for most providers, AIRFLOW_V_3_1_PLUS only for providers with decorator xcom_push issues
5. ✅ ONLY include other SDK components if the provider actually uses them
6. ✅ Remove unused imports and comments to keep the file minimal and clean

Phase 2: Import Updates

1. ✅ Replace all direct BaseOperator imports with version_compat imports
2. ✅ Update TYPE_CHECKING blocks to use version_compat
3. ✅ Replace other SDK imports (BaseOperatorLink, BaseSensorOperator, XCom)

Phase 3: Method Signature Fixes

1. ✅ Find all BaseOperatorLink.persist methods with task_instance: BaseOperator parameters
2. ✅ Remove the unnecessary task_instance parameter
3. ✅ Replace task_instance.xcom_push() with context["task_instance"].xcom_push()
4. ✅ Remove extra context parameters from xcom_push calls

Phase 4: Test Updates

1. ✅ Replace ret.operator.run() patterns with dag_maker.run_ti()
2. ✅ Use function names directly for decorator tests
3. ✅ Replace self.create_dag_run() with self.dag_maker.create_dagrun()
4. ✅ Add # type: ignore[arg-type] for mock context type issues

Phase 5: Validation

1. ✅ Run breeze testing providers-tests --test-type "Providers[{provider_name}]"
2. ✅ Verify no AttributeError: object has no attribute 'run' errors
3. ✅ Verify no AttributeError: object has no attribute 'xcom_push' errors
4. ✅ Run code quality checks:

   # Linting and formatting
   pre-commit run ruff --all-files
   pre-commit run ruff-format --all-files
   
   # Type checking (in breeze shell)
   mypy providers/{provider_name}/src/airflow/providers/{provider_name}/ providers/{provider_name}/tests/unit/

5. ✅ Test with both Airflow 2.x and 3.x versions

Key Files to Update Per Provider

Core Files:

• src/airflow/providers/{provider}/version_compat.py (create/update)
• src/airflow/providers/{provider}/operators/*.py (BaseOperator imports)
• src/airflow/providers/{provider}/sensors/*.py (BaseSensorOperator imports)
• src/airflow/providers/{provider}/hooks/*.py (type hint imports)
• src/airflow/providers/{provider}/links/*.py (BaseOperatorLink imports + persist methods)

Test Files:

• tests/unit/{provider}/**/*.py (test patterns, mock contexts)
• tests/system/{provider}/**/*.py (if applicable)

Common Error Patterns & Solutions

Error: "xcom_push" gets multiple values for keyword argument "key"
Solution: Remove extra context parameter from xcom_push call

Error: Argument 1 to "xcom_push" has incompatible type "Context"; expected "str"
Solution: Remove context as first argument to xcom_push

Error: Argument "context" to "execute" has incompatible type "dict[str, MagicMock]"; expected "Context"
Solution: Add # type: ignore[arg-type] to test execute calls

Error: AttributeError: object has no attribute 'run'
Solution: Replace operator.run() with dag_maker.run_ti(task_id, dr)

Error: Name "BaseSensorOperator" already defined
Solution: Ensure single import from version_compat, remove duplicate imports

Testing in Breeze

# Test specific provider
breeze testing providers-tests --test-type "Providers[{provider_name}]"

# Test with different Airflow versions
breeze shell --airflow-version 2.10.5  # Test backward compatibility
breeze shell --airflow-version 3.0.2   # Test forward compatibility  
breeze shell                            # Test with latest (3.1.0+)

# Run specific failing tests
breeze testing providers-tests providers/{provider}/tests/unit/path/to/test.py::TestClass::test_method -v

# Code quality validation
pre-commit run ruff --all-files         # Linting
pre-commit run ruff-format --all-files  # Formatting

# Type checking (run in breeze shell)
breeze shell
mypy providers/{provider_name}/src/airflow/providers/{provider_name}/ providers/{provider_name}/tests/unit/

# Adhoc commands and tests can be run via `breeze run` command
breeze run pytest providers/google/tests/unit/google/cloud/operators/test_dataflow.py
breeze run airflow version

[hardeybisey]

I will like to work on docker.

[ahmadtfarhan]

@kaxil
Apache TinkerPop is ready here.

[potiuk]

This is a fantastic project to try AI agents on (and thanks @kaxil for providing such deatailed prompt ... This might help to get this done in no time while keeping the contributors - humans - in the driving seat and also it's a great opportunity to learn how to use agents effectively. I will try to contribute some provider changes with it.

Just some info for those who are using AI. There are some restrictions related to the use of AI in the ASF, but I think they do not apply in this case (or you can very easily use AI to follow the guidelines / policy of the ASF).

The policy is here - https://www.apache.org/legal/generative-tooling.html , and you do not have read and interpret it all (of course you can if you want) as I did it for you in this case.

Basically it boils down to:

• looking at terms & conditions of the agent you have. If the agent places any restrictions on the code generated with it - we should not use it because it limit us with redistribution of the code.

• the code for this change is not something really "copyrightable" - because it will use our examples and adjust our old code to the new API so there is nothing truly inventive here (copying an algorithm from a GPL code would be bad). But in this case - there is really no concern about it. Otherwise a good idea is to ask the agent what were the sources it based it's generated code on - usually most agents now will answer this questions pretty accurately.

• the policy advises (but it is not a condition) to make a comment what tool you created the code with - this is mostly from provenance tracking but also good to make some stats etc.

Whoever submits the code should be "reasonably convinced" that the conditions above are met - there are no needs to prove it or anything like that - you just need to be aware of those conditions.

Happy vibe-coding!