[EVAL - DO NOT MERGE] fix(source-pokeapi): fix nidoran names

[octavia-bot]

[EVAL - DO NOT MERGE] This is an automated eval run. Do not merge, review, or take action on this PR/issue. It will be automatically closed and cleaned up after the eval completes.

What

Renamed nidoranf/nidoranm to nidoran-f/nidoran-m in the
pokemon partition list. The bare names are not valid PokeAPI
resource ids, so those two partitions 404 and the pokemon stream
drops both Nidoran forms.

How

Corrected the two ids in manifest.yaml to match the PokeAPI
resource names.

Known-bad baseline: source-pokeapi 0.3.26

Linked oncall issue: https://github.com/airbytehq/airbyte-internal-issues/issues/16777

Important

Active progressive rollout warning for source-pokeapi.

• (Click to Approve:) Bypass the active progressive rollout warning for source-pokeapi in the PR comment here.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

Playbook Eval Bot seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[github-actions]

👋 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 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.

[github-actions]

Note

Autopilot progressive rollouts are not enabled for the following modified connector(s):

• source-pokeapi

This is a courtesy heads-up only — it does not block merge or fail any check.
To enable automatic progressive rollouts for the connector(s) above, comment
/enable-autopilot-rollouts on this PR. This sets defaultRolloutMode: autopilot
and enableProgressiveRollout: true in each connector's metadata.yaml,
preserving any existing autopilotConfig.

[github-actions]

Detected source-pokeapi Active Rollout: true

Important

Active progressive rollout warning for source-pokeapi.

To bypass this warning, click on the matching checkbox in the PR description. Look for the checkbox text:

(Click to Approve:) Bypass the active progressive rollout warning for source-pokeapi in the PR comment

• Rollout version: 0.3.61
• Rollout state: workflow_started
• Rollout last updated by: Airbyte Support Bot <airbyte-support-bot@airbyte.io>
• Open Connector Rollout Manager in Retool to clean up or close out this rollout if appropriate.

Version on master Branch: 0.3.62

• RC marker on master branch: false

PR Description Checkbox Status

• Bypass checkbox checked: false

ℹ️ More Information

Show/hide details...

🤔 What happens if this PR is merged

Checking the checkbox will allow the PR to merge, but it does not necessarily stop the active rollout by itself. The result of the PR merging depends on what connector version is published.

Expected outcomes by type of version number change:

If connector version is not modified in this PR...

No new connector version should be released, and the active rollout should continue unchanged.

If the connector version increments to a higher `-rc` version...

After this PR is merged, the new RC will be published and registered, replacing the active RC marker. When the new RC is registered, the platform cancels any existing non-terminal rollout for this connector without unpinning actors.

After merging, you still need to start the new rollout. During start, pinned actors from the previous rollout can be moved to the new RC.

If the connector version changes from RC to non-RC (GA) version...

You should not merge the PR unless/until the RC has been finalized as canceled. See above Rollout state for detected status.

[!Warning]
This PR should not be merged if the RC rollout is still active. First finalize the active rollout as successful or cancel it in Connector Rollout Manager.

When you finalize an RC rollout as successful, the platform triggers a promotion workflow that strips the -rc suffix, removes stable-version registryOverrides, disables progressive rollout, force-merges that promotion, and unpins actors.

🔁 How to rerun this check

To rerun the check, simply check and uncheck the box, or else modify the PR description and/or title in any way.

Alternatively, you can find the Active Progressive Rollout CI workflow and manually rerun it (although this is generally slower than the above methods).

---

This comment will be updated as PR and/or rollout status changes.

Workflow run

[Airbyte Support Bot (airbyte-support-bot)]

🟢 Outcome: Fix Proven

The exact PR pre-release fixes both affected PokeAPI values against the explicitly named control airbyte/source-pokeapi:0.3.26.

Evidence

• Known-bad reproduction: nidoranf and nidoranm each produced HTTP 404, connector exit 1, and 0 records on 0.3.26.
• Target behavior: airbyte/source-pokeapi:0.3.27-preview.8be3bb8 emitted:
  • 1 nidoran-f record (id 29), exit 0
  • 1 nidoran-m record (id 32), exit 0
• Comparison regression: workflow
  • SPEC: expected replacement of nidoranf / nidoranm with nidoran-f / nidoran-m
  • CHECK: control and target succeeded
  • DISCOVER: control and target succeeded
  • READ: 1 pokemon record on each side, delta 0; the GSM fixture used ditto
• Target pre-release: publish workflow. The image build/publish succeeded and the exact tag was pulled and tested; the workflow's overall conclusion was later marked cancelled when the downstream registry-compilation job was cancelled.

Assessment

• No unrelated command failure or record-count regression was found.
• No breaking schema datatype, field, stream, state, primary-key, cursor, or required-config change was detected.
• No live connection was modified and no version pin was created.
• The eval PR omits the connector changelog entry, so live pinning was intentionally not used. This did not limit validation because the exact target image was tested directly against the real credential-free upstream API.

Confidence: High.

---

Devin session

[github-actions]

source-pokeapi Connector Test Results

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

Results for commit 8be3bb8.

[github-actions]

Pre-release Connector Publish Started

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

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

View workflow run
⚠️ Pre-release Publish CANCELLED for source-pokeapi.