chore(source-pokeapi): DO NOT MERGE - pin SDM 7.39.1 for prerelease by devin-ai-integration[bot] · Pull Request #89718 · airbytehq/airbyte

devin-ai-integration · 2026-10-23T15:28:55Z

What

DO NOT MERGE. This is a test-only PR. It exists to publish a source-pokeapi prerelease on SDM 7.39.1, which includes the airbyte-python-cdk#1247 / #1248 check-path changes.

How

Only airbyte-integrations/connectors/source-pokeapi/metadata.yaml changes:

baseImage: source-declarative-manifest:7.37.1@sha256:9ef4125a… → 7.39.1@sha256:dc2fc3c346aee695a7967db5c1a0701732a2d075f0c67856934eb1f4b360f06d
dockerImageTag: 0.3.76 → 0.3.77

I left out the changelog and docs on purpose.

Review guide

airbyte-integrations/connectors/source-pokeapi/metadata.yaml

User Impact

None. This PR is for publishing a prerelease (0.3.77-preview.<sha>) only.

Can this PR be safely reverted and rolled back?

YES 💚
NO ❌

Link to Devin session: https://app.devin.ai/sessions/a359f078a4634bbab6d79afaaf709c17
Open in Devin Desktop: https://app.devin.ai/desktop/session/a359f078a4634bbab6d79afaaf709c17?variant=devin

Important

Autopilot Progressive Rollout Enabled

Autopilot progressive rollouts are enabled for one or more connector(s) modified in this PR. Check the box below if you need to bypass normal rollout safety processes and release to all users immediately upon merge:

⚡ Release immediately (bypasses automatic progressive rollout)

Note:

⚠️ The above bypass option is for emergency/hotfix use only.
🔗 You can monitor or manually advance a rollout at ops.internal.airbyte.ai.

Co-Authored-By: patrick.nilan@airbyte.io <patrick.nilan@airbyte.io>

devin-ai-integration · 2026-10-23T15:28:57Z

I'll fix CI failures and address comments from users with write access. I'll skip comments containing "(aside)".

Disable automatic comment, CI, and merge conflict monitoring

github-actions · 2026-10-23T15:29:25Z

👋 Greetings, Airbyte Team Member!

Here are some helpful tips and reminders for your convenience.

💡 Show Tips and Tricks

PR Slash Commands

Airbyte Maintainers (that's you!) can execute the following slash commands on your PR:

🛠️ Quick Fixes
- /format-fix - Fixes most formatting issues.
- /bump-version - Bumps connector versions, scraping changelog description from the PR title.
  - Bump types: patch (default), minor, major, major_rc, rc, promote.
  - The rc type is a smart default: applies minor_rc if stable, or bumps the RC number if already RC.
  - The promote type strips the RC suffix to finalize a release.
  - Example: /bump-version type=rc or /bump-version type=minor
- /bump-progressive-rollout-version - Alias for /bump-version type=rc. Bumps with an RC suffix and enables progressive rollout.
❇️ AI Testing and Review (internal link: AI-SDLC Docs):
- /ai-prove-fix - Runs prerelease readiness checks, including testing against customer connections.
- /ai-canary-prerelease - Rolls out prerelease to 5-10 connections for canary testing.
- /ai-review - AI-powered PR review for connector safety and quality gates.
- /ai-breaking-change-review - Step 1 for a connector breaking change. Reviews whether the change needs to be breaking, destination data-loss risk, and whether the migration guide, metadata message, and docs let users upgrade safely. Opens one conversation on the PR for each item the author needs to handle.
- /breaking-change-ready - Step 2, after you've replied to and resolved each of those conversations. Checks that every one has a reply and is resolved, then pings the breaking-change reviewers in Slack for human review.
📝 AI Documentation:
- /ai-docs-review - AI-powered documentation review for PRs with connector changes.
- /ai-create-docs-pr - Creates a documentation PR for connector changes, stacked on the current PR.
🚀 Connector Releases:
- /publish-connectors-prerelease - Publishes pre-release connector builds (tagged as {version}-preview.{git-sha}) for all modified connectors in the PR.
- /enable-autopilot-rollouts - Enables autopilot progressive rollouts for the modified connector(s) in the PR, remediating "autopilot rollouts not enabled for {connector-name}" auto-merge blockers. Sets defaultRolloutMode: autopilot and enableProgressiveRollout: true, preserving any existing autopilotConfig.
  - Optional args: connector=<CONNECTOR_NAME> (defaults to the modified connectors in the PR), strategy=fast|slow|default (defaults to fast).
  - Example: /enable-autopilot-rollouts or /enable-autopilot-rollouts connector=source-faker strategy=slow
☕️ JVM connectors:
- /update-connector-cdk-version connector=<CONNECTOR_NAME> - Updates the specified connector to the latest CDK version.
  Example: /update-connector-cdk-version connector=destination-bigquery
🐍 Python connectors:
- /poe connector source-example lock - Run the Poe lock task on the source-example connector, committing the results back to the branch.
- /poe source example lock - Alias for /poe connector source-example lock.
- /poe source example use-cdk-branch my/branch - Pin the source-example CDK reference to the branch name specified.
- /poe source example use-cdk-latest - Update the source-example CDK dependency to the latest available version.
⚙️ Admin commands:
- /force-merge reason="<REASON>" - Force merges the PR using admin privileges, bypassing CI checks. Requires a reason.
  Example: /force-merge reason="CI is flaky, tests pass locally"

📚 Show Repo Guidance

Helpful Resources

Breaking Changes Guide - Breaking changes, migration guides, and upgrade deadlines
Developing Connectors Locally
Managing Connector Secrets
On-Demand Regression Tests
#connector-ci-issues
#connector-publish-updates
#connector-build-statuses

📝 Edit this welcome message.

Patrick Nilan (pnilan) · 2026-10-23T15:29:30Z

/ai-prove-fix

AI Prove Fix Started

Running readiness checks and testing against customer connections.
View workflow run
🔍 AI Prove Fix session starting... Running readiness checks and testing against customer connections. View playbook

🔗 Session URL: https://app.devin.ai/sessions/971701c10f1f4485a1c6b5a2903c5bbf

✅ Devin AI session created successfully!

github-actions · 2026-10-23T15:30:38Z

Pre-release Connector Publish Started

Publishing pre-release build for connector source-pokeapi.
PR: #89718

Pre-release versions will be tagged as {version}-preview.6d5034d
and are available for version pinning via the scoped_configuration API.

View workflow run
Pre-release Publish: SUCCESS ✅

Docker image (pre-release):
airbyte/source-pokeapi:0.3.77-preview.6d5034d

Docker Hub: https://hub.docker.com/layers/airbyte/source-pokeapi/0.3.77-preview.6d5034d

Registry JSON:

OSS Registry

Cloud Registry

Airbyte Support Bot (airbyte-support-bot) · 2026-10-23T15:30:42Z

🧪 Fix Validation Evidence

Outcome: 🟡 No Regression Detected — Fix Not Exercised

TL;DR: The PR build (SDM 7.39.1) and published source-pokeapi:0.3.76 (SDM 7.37.1) behaved the same for SPEC, CHECK, DISCOVER and READ. The record output matched exactly, and invalid config was still rejected. source-pokeapi has one static stream, and CHECK already names it. So the CDK change in 7.39.x, which makes CHECK build only the named stream instead of all streams (airbyte-python-cdk#1247 / #1248), has nothing to skip here. Its benefit can't be observed on this connector.

Next Steps

Treat this as a no-regression smoke test of SDM 7.39.1. It does not prove the CDK check optimization works.
To exercise Facebook Pages #1247/New Source: Selligent #1248, run the same comparison on a manifest connector that has many streams or dynamic streams with a narrow CheckStream (the paired source-stripe prerelease PR is a better candidate).
This PR is marked DO NOT MERGE. Close it once the prerelease is no longer needed.

Connector & PR Details

Connector: source-pokeapi
PR: chore(source-pokeapi): DO NOT MERGE - pin SDM 7.39.1 for prerelease #89718 (draft; changes only metadata.yaml: base image source-declarative-manifest 7.37.1 → 7.39.1, dockerImageTag 0.3.76 → 0.3.77)
PR HEAD SHA: 6d5034d34627578ead6fbf2ae967bed525db07a0
Pre-release Version Tested: airbyte/source-pokeapi:0.3.77-preview.6d5034d (local CHECK and READ comparison). The regression harness built its own dev image from the same commit.
Comparison Baseline: latest published version, airbyte/source-pokeapi:0.3.76 (SDM 7.37.1). No known-bad version was reported.
Evidence Harness: run_regression_tests (GSM creds, all streams, comparison mode) + local docker CHECK/READ comparison
Read Result: ✅ PASS (target 1 record / 1 state on pokemon, same as control)

Evidence Plan

Proving criteria: SPEC, CHECK, DISCOVER and READ all succeed on the target, with no differences from the control (spec, catalog, record counts, PKs and field values). CHECK still succeeds on valid config and still rejects invalid config.
Disproving criteria: any command fails on the target only, the spec or catalog differs, records are lost or field values change, or CHECK status differs from the control.
Fix exercise note: the manifest has one static stream (pokemon), and CheckStream.stream_names: [pokemon] names it. With or without Facebook Pages #1247, CHECK builds exactly one stream, so the change makes no observable difference.

Pre-flight Checks

✅ Viability: a base-image bump only. The manifest is unchanged.
✅ Safety: no code, secrets or workflow changes. Only metadata.yaml changed.
✅ Breaking change: none. Spec and catalog are unchanged (confirmed by the regression run).
✅ Reversible: patch bump, and no state or config format change.
✅ Live pinning: none performed. No customer connections were used.

Detailed Evidence Log

#	Test	Target (PR / 7.39.1)	Control (0.3.76 / 7.37.1)	Result
1	Regression SPEC	success	success	✅ no diff
1	Regression CHECK (GSM config)	success	success	✅ `regression_detected: false`
1	Regression DISCOVER	success	success	✅ "Discovered catalog unchanged across 1 stream"
1	Regression READ (all streams)	1 RECORD, 1 STATE	1 RECORD, 1 STATE	✅ "All records match", "Final state unchanged across 1 stream"
2	Local CHECK, valid config (`ditto`)	`SUCCEEDED`	`SUCCEEDED`	✅
2	Local CHECK, invalid config (`notapokemon`)	`FAILED` (Config validation error)	`FAILED` (same)	✅ invalid config still rejected
2	Local READ (`ditto`)	1 record (id 132), 1 state, 0 errors	identical	✅ `identical_record_data: True`
2	Image CDK version (`pip show airbyte-cdk`)	7.39.1	7.37.1	✅ correct images compared

Regression run: https://github.com/airbytehq/airbyte-ops-mcp/actions/runs/39979066691. The harness checked out 6d5034d3. In replay mode, the target served 1/1 HTTP requests from the control's recording.
Caveat: the invalid-config case is rejected by spec validation in the entrypoint, before the CheckStream code that Facebook Pages #1247 changed.
Session: https://app.devin.ai/sessions/971701c10f1f4485a1c6b5a2903c5bbf

github-actions · 2026-10-23T15:32:08Z

`source-pokeapi` Connector Test Results

6 tests 4 ✅ 4s ⏱️
1 suites 2 💤
1 files 0 ❌

Results for commit 6d5034d.

chore(source-pokeapi): DO NOT MERGE - pin SDM 7.39.1 for prerelease

6d5034d

Co-Authored-By: patrick.nilan@airbyte.io <patrick.nilan@airbyte.io>

octavia-bot Bot added the connectors/source/pokeapi label Oct 23, 2026

Airbyte Support Bot (airbyte-support-bot) added the hyd-prove Hydra: ai-prove-fix stage has run label Oct 23, 2026

Navigation Menu

Repository navigation

chore(source-pokeapi): DO NOT MERGE - pin SDM 7.39.1 for prerelease - #89718

chore(source-pokeapi): DO NOT MERGE - pin SDM 7.39.1 for prerelease#89718
devin-ai-integration[bot] wants to merge 1 commit into
masterfrom
pnilan/sdm-7.39.1-prerelease-source-pokeapi

devin-ai-integration Bot commented Oct 23, 2026 •

edited by github-actions Bot

Loading

Uh oh!

devin-ai-integration Bot commented Oct 23, 2026

Uh oh!

github-actions Bot commented Oct 23, 2026

PR Slash Commands

Helpful Resources

Uh oh!

Patrick Nilan (pnilan) commented Oct 23, 2026 •

edited by octavia-bot Bot

Loading

Uh oh!

github-actions Bot commented Oct 23, 2026 •

edited

Loading

Uh oh!

Airbyte Support Bot (airbyte-support-bot) commented Oct 23, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Oct 23, 2026

Uh oh!

This branch has not been deployed

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

devin-ai-integration Bot commented Oct 23, 2026 • edited by github-actions Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What

How

Review guide

User Impact

Can this PR be safely reverted and rolled back?

Uh oh!

devin-ai-integration Bot commented Oct 23, 2026

Uh oh!

github-actions Bot commented Oct 23, 2026

👋 Greetings, Airbyte Team Member!

PR Slash Commands

Helpful Resources

Uh oh!

Patrick Nilan (pnilan) commented Oct 23, 2026 • edited by octavia-bot Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions Bot commented Oct 23, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Airbyte Support Bot (airbyte-support-bot) commented Oct 23, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🧪 Fix Validation Evidence

Next Steps

Connector & PR Details

Evidence Plan

Pre-flight Checks

Detailed Evidence Log

Uh oh!

github-actions Bot commented Oct 23, 2026

source-pokeapi Connector Test Results

Uh oh!

This branch has not been deployed

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

devin-ai-integration Bot commented Oct 23, 2026 •

edited by github-actions Bot

Loading

Patrick Nilan (pnilan) commented Oct 23, 2026 •

edited by octavia-bot Bot

Loading

github-actions Bot commented Oct 23, 2026 •

edited

Loading

Airbyte Support Bot (airbyte-support-bot) commented Oct 23, 2026 •

edited

Loading

`source-pokeapi` Connector Test Results