Skip to content

docs(source-amazon-seller-partner): Add GET_SALES_AND_TRAFFIC_REPORT_BY_DATE to supported streams and fix changelog date#74068

Draft
devin-ai-integration[bot] wants to merge 1 commit intomasterfrom
devin/1772126357-amazon-seller-partner-docs
Draft

docs(source-amazon-seller-partner): Add GET_SALES_AND_TRAFFIC_REPORT_BY_DATE to supported streams and fix changelog date#74068
devin-ai-integration[bot] wants to merge 1 commit intomasterfrom
devin/1772126357-amazon-seller-partner-docs

Conversation

@devin-ai-integration
Copy link
Contributor

What

Updates the Amazon Seller Partner connector documentation to reflect the new GET_SALES_AND_TRAFFIC_REPORT_BY_DATE stream added in #72258. That PR added the stream to the connector manifest and a changelog entry, but did not add it to the Supported Streams list. Also corrects the changelog date for v5.5.0.

Note: I am an AI agent (Devin). I have proposed these documentation updates based on recent changes to this connector. Reviewers may merge, modify, or close this PR as they see fit.

How

  1. Added "Sales and Traffic Business Report (By Date)" to the Supported Streams section, following the naming pattern established by the existing "(Monthly)" variant.
  2. Fixed the v5.5.0 changelog date from 2026-02-25 to 2026-02-26 to match the actual merge date of PR feat(source-amazon-seller-partner): Add GET_SALES_AND_TRAFFIC_REPORT_BY_DATE stream #72258.
  3. Cleaned up the v5.5.0 changelog description to remove the commit-style feat(...) prefix and add user-facing context.

Review guide

  1. docs/integrations/sources/amazon-seller-partner.md — only file changed

Items for reviewer to verify:

  • Is "Sales and Traffic Business Report (By Date)" the right user-facing name for the GET_SALES_AND_TRAFFIC_REPORT_BY_DATE stream? It follows the convention of the "(Monthly)" variant but the reviewer should confirm this is clear enough to distinguish from the base stream (which extracts ASIN-level data, not date-level aggregated data).
  • Confirm 2026-02-26 is the correct merge date for feat(source-amazon-seller-partner): Add GET_SALES_AND_TRAFFIC_REPORT_BY_DATE stream #72258.

User Impact

Users will now see the new GET_SALES_AND_TRAFFIC_REPORT_BY_DATE stream listed in the connector documentation, making it discoverable.

Can this PR be safely reverted and rolled back?

  • YES 💚

Link to Devin run: https://app.devin.ai/sessions/cc9559651bdb49d1b592790e3ec182d0
Requested by: bot_apk (apk@cognition.ai)

…BY_DATE to supported streams and fix changelog date

Co-Authored-By: bot_apk <apk@cognition.ai>
@devin-ai-integration
Copy link
Contributor Author

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
  • Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

  • Disable automatic comment and CI monitoring

@github-actions
Copy link
Contributor

👋 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.
  • ❇️ 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.
  • 🚀 Connector Releases:
    • /publish-connectors-prerelease - Publishes pre-release connector builds (tagged as {version}-preview.{git-sha}) for all modified connectors in the PR.
    • /bump-progressive-rollout-version - Bumps connector version with an RC suffix (2.16.10-rc.1) for progressive rollouts (enableProgressiveRollout: true).
      • Example: /bump-progressive-rollout-version changelog="Add new feature for progressive rollout"
  • ☕️ 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
    • /bump-bulk-cdk-version bump=patch changelog='foo' - Bump the Bulk CDK's version. bump can be major/minor/patch.
  • 🐍 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

📝 Edit this welcome message.

@github-actions
Copy link
Contributor

Deploy preview for airbyte-docs ready!

✅ Preview
https://airbyte-docs-q89vazuor-airbyte-growth.vercel.app

Built with commit 494ea43.
This pull request is being automatically deployed with vercel-action

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/documentation Improvements or additions to documentation team/documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants