Add lockstep release workflow to main (dispatch-only) - #455
Merged
Conversation
Cherry-picked from the pubsub-split/release-tooling branch (d24039b, workflow file only): workflow_dispatch workflows are only registered once the file exists on the default branch, so this must land on main before release runs can be dispatched against the integration branches (gh workflow run release.yml --ref <branch>). Inert on main: dispatch-only, and its pre-flight fails on main's layout (no core/ or server/ gems), so nothing can be published from here. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
umair-ably
marked this pull request as ready for review
September 2, 2026 12:13
AndyTWF
approved these changes
Sep 2, 2026
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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
Cherry-picks
.github/workflows/release.yml(only the workflow file) from #454 ontomain.Why
workflow_dispatchworkflows are only registered once the file exists on the default branch. The Pub/Sub split work merges tointegration/v2and won't reachmainuntil GA, so without this the release workflow cannot be dispatched at all — including the initial run that claims theably-pubsub-core/ably-pubsub-servergem names on RubyGems via trusted publishing and proves the OIDC pipeline end to end (gh workflow run release.yml --ref <branch>).Safety on main
The workflow is inert here:
core/andserver/gem layouts, which don't exist onmain, so a dispatch atmainfails before anything is built or pushed.The full release tooling (pre-flight, dry-run CI job, docs) is reviewed in #454; this PR is purely the registration mechanism.
🤖 Generated with Claude Code