[octavia-bot-hoard]

Updates dependencies for source-amazon-seller-partner.

Updated packages: N/A

🤖 Generated by automated workflow job.

Important

⚡ Auto-merge enabled.

This PR is set to merge automatically when all requirements are met.

Note

Auto-merge may have been disabled. Please check the PR status to confirm.

[octavia-bot-admin]

Auto-approved by connectors up-to-date workflow.

[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-amazon-seller-partner

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]

Deploy preview for airbyte-docs ready!

Project:	airbyte-docs
Status:	✅  Deploy successful!
Preview URL:	https://airbyte-docs-ejeub9dpz-airbyte-growth.vercel.app
Latest Commit:	64cde8b

Deployed with vercel-action

[github-actions]

source-amazon-seller-partner Connector Test Results

596 tests   593 ✅  22m 18s ⏱️
  2 suites    3 💤
  2 files      0 ❌

Results for commit 64cde8b.

♻️ This comment has been updated with latest results.

[devin-ai-integration]

Auto-merge disabled — do not merge until the CDK regression is fixed

Auto-merge has been disabled on this PR at Daryna Ishchenko (@darynaishchenko)'s request. It is on hold, not rejected.

Why: this PR bumps the base image to source-declarative-manifest:7.23.7. That SDM version contains a CDK regression (airbytehq/airbyte-python-cdk#1082) which makes every class_name reference in a manifest require AIRBYTE_ENABLE_UNSAFE_CODE=true — including components bundled inside the connector's own published image. Airbyte Cloud deliberately never sets that variable, so any connector built on 7.23.7 that resolves a custom component fails check, discover and read immediately with:

AirbyteCustomCodeNotPermittedError: Custom connector code is not permitted in this environment.

source-amazon-seller-partner bundles a components.py and resolves the following classes from its manifest, so merging this would break it in Cloud:

• AmazonSPOauthAuthenticator
• AmazonSPRdtAuthenticator
• AmazonSellerPartnerWaitTimeFromHeaderBackoffStrategy
• FlatFileSettlementV2ReportsTypeTransformer
• GetXmlBrowseTreeDataDecoder
• GzipCsvDecoder
• GzipJsonDecoder
• GzipXmlDecoder
• LedgerDetailedViewReportsTypeTransformer
• MerchantListingsFypReportTypeTransformer
• MerchantReportsTypeTransformer
• ReportCreationRequester
• SellerFeedbackReportsGzipCsvDecoder
• SellerFeedbackReportsTypeTransformer
• ValidateReportOptionsListOptionNameUniqueness
• ValidateReportOptionsListStreamNameUniqueness

This already happened today: 27 sources were published onto 7.23.7 by the Connectors up-to-date pipeline and broke in Cloud, requiring emergency Cloud registry rollbacks (#83183 and #83187) plus per-workspace version pins for affected customers.

When this can merge: after airbytehq/airbyte-python-cdk#1083 is merged, released, and a new SDM base image containing the fix is published. At that point re-run Connectors up-to-date for this connector (or just rebase) so it picks up the fixed base image, then re-enable auto-merge.

The dependency bumps in this PR are otherwise fine — only the base image pin is the problem.

---

Devin session

[devin-ai-integration]

Updated the base image on this branch to source-declarative-manifest:7.23.8, which contains the fix for the regression this PR was put on hold for (airbytehq/airbyte-python-cdk#1083, released as CDK 7.23.8). source-amazon-seller-partner bundles a components.py, so on 7.23.7 it would have failed check/discover/read in Cloud with AirbyteCustomCodeNotPermittedError.

The 27 sources that were rolled back in Cloud have already been moved to 7.23.8 and had their temporary registryOverrides.cloud.dockerImageTag removed in #83194.

Auto-merge is still disabled on this PR — re-enable it whenever you're ready; the blocking reason is gone.

Requested by Daryna Ishchenko (@darynaishchenko).

---

Devin session