Thanks to visit codestin.com
Credit goes to github.com

Skip to content

test(source-greenhouse): Validate rollout gate with active rollout#78020

Draft
Aaron ("AJ") Steers (aaronsteers) wants to merge 3 commits into
masterfrom
devin/1778560893-rollout-gate-active-test
Draft

test(source-greenhouse): Validate rollout gate with active rollout#78020
Aaron ("AJ") Steers (aaronsteers) wants to merge 3 commits into
masterfrom
devin/1778560893-rollout-gate-active-test

Conversation

@aaronsteers
Copy link
Copy Markdown
Member

@aaronsteers Aaron ("AJ") Steers (aaronsteers) commented May 12, 2026 •
edited
Loading

What

Test the merged progressive rollout gate workflow against source-greenhouse, which currently has an active rollout.

This PR is intentionally for E2E validation only and should not be merged.

How

Adds a temporary README sentence under airbyte-integrations/connectors/source-greenhouse/ so the connector matrix includes source-greenhouse.

Review guide

  1. airbyte-integrations/connectors/source-greenhouse/README.md
  2. Connector Active Progressive Rollout Checks workflow result
  3. Progressive rollout gate PR comment and PR-description ACK checkbox

User Impact

No intended user impact. This PR is test-only and should be closed after validation.

Can this PR be safely reverted and rolled back?

  • YES 💚
  • NO ❌

Link to Devin session: https://app.devin.ai/sessions/13ae42611c254ef8a91c77ddc207bbb6
Requested by: Aaron ("AJ") Steers (@aaronsteers)

Important

Active progressive rollout warning for source-greenhouse.

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

@devin-ai-integration
Copy link
Copy Markdown
Contributor

devin-ai-integration Bot commented May 12, 2026

🤖 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
Copy Markdown
Contributor

github-actions Bot commented May 12, 2026

👋 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.
  • ☕️ 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

📝 Edit this welcome message.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 12, 2026 •
edited
Loading

Detected source-greenhouse Active Rollout: true

Important

Active progressive rollout warning for source-greenhouse.

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-greenhouse in the PR comment

  • Rollout version: 0.7.22-rc.2
  • Rollout state: in_progress

Version on master Branch: 0.7.22-rc.2

  • 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 changes from RC to non-RC (GA) version...

The merged PR may publish the GA version and make it default for eligible non-pinned actors. The existing rollout is not stopped immediately by the merge, but the rollout worker can later cancel it as superseded when finalizing.

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

The merged PR may publish a new release candidate and replace the active RC marker. The previous incomplete rollout is canceled without unpinning, and a new rollout is created for the subsequent RC version.

🔁 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

@devin-ai-integration devin-ai-integration Bot mentioned this pull request May 12, 2026
Merged
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

@aaronsteers Aaron ("AJ") Steers (aaronsteers)

Labels

connectors/source/greenhouse

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@aaronsteers @octavia-squidington-iii