You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
☕️ 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"
Active progressive rollout warning for destination-s3.
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 destination-s3 in the PR comment
Rollout version: 1.9.8-rc.1
Rollout state: workflow_started
Version on master Branch: 1.9.8-rc.1
RC marker on master branch: true
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.
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Cuts s3 release since the progressive rollout tool isn't working
Important
Active progressive rollout warning for destination-s3.