bug: airbyte-api 1.0.0 has forward-reference errors and breaking API changes vs 0.53.0

[devin-ai-integration]

Summary

airbyte-api==1.0.0 introduces three categories of breaking changes that prevent PyAirbyte from upgrading. Full regression test results are in airbytehq/PyAirbyte#1048.

1. Forward-reference errors in generated models (code generation bug)

Two models have forward-reference issues where classes/enums are used before they are defined:

SourceResponse — NameError on import

from airbyte_api.models import SourceResponse
# NameError: name "SourceGoogleAnalyticsDataAPISchemasCustomReportsArrayDimensionFilter
# DimensionsFilter2ExpressionsFilterFilter4ToValueValueType" is not defined

Root cause: In source_google_analytics_data_api_schemas_custom_reports_array_int64value.py, the enum ...Filter4ToValueValueType is referenced at line 1422 (inside a class body) but defined at line 1457. Python evaluates class bodies eagerly, so the name is not yet available.

ConnectionResponse — PydanticUserError on construction

models.ConnectionResponse(connection_id="x", ...)
# pydantic.errors.PydanticUserError: `ConnectionResponse` is not fully defined;
# you should define `RowFilteringOperationNot`, then call `ConnectionResponse.model_rebuild()`.

Root cause: Same class of issue — a Pydantic model references RowFilteringOperationNot as a forward reference, but it has not been resolved when the model is first used.

Both are code-generation ordering bugs — the Speakeasy generator is emitting class definitions in the wrong order.

2. API method signatures changed to keyword-only arguments

All SDK resource methods (e.g., Workspaces.get_workspace, Sources.create_source, Jobs.list_jobs, etc.) now require request= to be passed as a keyword argument. In 0.53.0, positional passing was allowed. This is a breaking change for all existing callers.

Example — this worked in 0.53.0 but fails in 1.0.0:

# 0.53.0 (works)
api_instance.workspaces.get_workspace(api.GetWorkspaceRequest(workspace_id="..."))

# 1.0.0 (requires keyword)
api_instance.workspaces.get_workspace(request=api.GetWorkspaceRequest(workspace_id="..."))

Pyrefly reports 39 type errors across airbyte/_util/api_util.py: [unexpected-positional-argument], [bad-argument-count], and [bad-argument-type].

3. Response type changes break duck-typing protocols

Response objects (e.g., CreateWorkspaceResponse, ListJobsResponse, PatchSourceResponse) have a changed .raw_response type that is no longer structurally compatible with PyAirbyte's AirbyteApiResponseDuckType protocol. Pyrefly reports these as [bad-argument-type] errors.

Impact

• 474 of 484 tests pass when the 2 broken test modules are excluded
• All 7 required CI checks fail on the full suite
• Core imports (ConnectionResponse, DestinationResponse, JobResponse, WorkspaceResponse, JobStatusEnum) work fine
• The forward-reference issues (chore: speakeasy sdk regeneration - Generate #1) are bugs in the SDK itself; the signature changes (chore: speakeasy sdk regeneration - Generate #2, chore: speakeasy sdk regeneration - Generate #3) require PyAirbyte code updates

Reproduction

pip install airbyte-api==1.0.0
python -c "from airbyte_api.models import SourceResponse"  # NameError

Environment

• Python 3.10, 3.11, 3.12 (all affected)
• Ubuntu and Windows (all affected)
• airbyte-api 0.53.0 → 1.0.0

---

Devin session

[devin-ai-integration]

Update: tested airbyte-api==1.0.0rc2

Retested PyAirbyte against 1.0.0rc2 (https://pypi.org/project/airbyte-api/1.0.0rc2/).

Show/Hide Detailed Report

Fixed in rc2

SourceResponse import NameError — The forward-reference ordering bug in source_google_analytics_data_api_schemas_custom_reports_array_int64value.py is resolved. from airbyte_api.models import SourceResponse now works.

Still broken in rc2

1. ConnectionResponse Pydantic forward-reference

models.ConnectionResponse(connection_id="x", ...)
# PydanticUserError: `ConnectionResponse` is not fully defined;
# you should define `RowFilteringOperationNot1`, then call `ConnectionResponse.model_rebuild()`.

Same class of code-generation ordering bug as the original SourceResponse issue, but for a different model (RowFilteringOperationNot1).

2. Keyword-only request= argument (breaking API change)

All SDK resource methods now require request= as a keyword argument. Pyrefly reports 39 type errors. This is a breaking change vs 0.53.0.

3. Response type .raw_response incompatibility

Response objects have a changed .raw_response type that breaks structural typing / duck-type protocols.

New in rc2

4. UsernameAndPassword renamed to DestinationSnowflakeUsernameAndPassword

from airbyte_api.models import UsernameAndPassword
# ImportError: cannot import name 'UsernameAndPassword'

The generic UsernameAndPassword model was renamed to DestinationSnowflakeUsernameAndPassword. This blocks PyAirbyte's entire test suite from collecting (the import is in airbyte/caches/_utils/_cache_to_dest.py, which is imported transitively by airbyte/__init__.py).

Test results with rc2

After patching the UsernameAndPassword import and excluding 2 test files blocked by the ConnectionResponse forward-ref:

• 479 passed, 3 failed (pyrefly type errors from keyword-only args + ruff lint from the import patch), 1 skipped
• Core functionality works; regressions are confined to the issues listed above

Summary

Issue	Status in 1.0.0	Status in 1.0.0rc2
SourceResponse NameError	Broken	Fixed
ConnectionResponse PydanticUserError	Broken	Still broken
Keyword-only request= args	Breaking	Still breaking
.raw_response type change	Breaking	Still breaking
UsernameAndPassword renamed	N/A	New regression

Requested by Aaron ("AJ") Steers (@aaronsteers).

---

Devin session

[devin-ai-integration]

Confirmed bug in 1.0.0rc2: missing ConnectionResponse.model_rebuild()

Tested airbyte-api==1.0.0rc2. The SourceResponse NameError from 1.0.0 is fixed, but there is one remaining confirmed code-gen bug:

ConnectionResponse cannot be instantiated — PydanticUserError

from airbyte_api import models
models.ConnectionResponse(connection_id="x", ...)
# PydanticUserError: `ConnectionResponse` is not fully defined;
# you should define `RowFilteringOperationNot1`, then call `ConnectionResponse.model_rebuild()`.

Root cause: RowFilteringOperationNot1 exists in the package (airbyte_api.models.rowfilteringoperationnot_1), and RowFilteringOperationNot1.model_rebuild() is called in models/__init__.py (line 4927). However, ConnectionResponse.model_rebuild() is never called, so Pydantic cannot resolve the forward reference when ConnectionResponse is first used.

# models/__init__.py
4927: RowFilteringOperationNot1.model_rebuild()   # ← this exists
# ConnectionResponse.model_rebuild()              # ← this is missing

Fix: Add ConnectionResponse.model_rebuild() to the model_rebuild() section of models/__init__.py (or fix the Speakeasy generator to emit it).

Note: The other issues from the original report (keyword-only request= args, requests.Response → httpx.Response, UsernameAndPassword rename) are intentional breaking changes, not bugs.

Reported by Aaron ("AJ") Steers (@aaronsteers).

---

Devin session