Add lockstep release workflow and migration docs - #454
Draft
umair-ably wants to merge 2 commits into
Draft
Conversation
umair-ably
force-pushed
the
pubsub-split/release-tooling
branch
from
September 1, 2026 16:06
7c49e75 to
a48d85e
Compare
- release.yml publishes ably-pubsub-core and ably-pubsub-server at the same version via RubyGems trusted publishing (OIDC, no long-lived keys). A pre-flight fails before anything is pushed if the version input, either gem's version constant, or the server gem's exact core pin disagree. Partial releases fail reversibly: re-running with the same version skips already-published gems. - CONTRIBUTING.md documents the two-gem layout and the new release process; the manual rake release and the ably-ruby-rest step are gone (both legacy gems are maintenance-only per PDR-091b). - UPDATING.md gains the 1.x -> 2.0 migration section with the old-name -> new-name mapping table, marked draft pending PDR-091d. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Runs the same version-consistency assertions as release.yml's pre-flight and builds both gems on every PR, so a version-file or gemspec regression surfaces immediately instead of at release time. Publishes nothing. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
umair-ably
force-pushed
the
pubsub-split/release-tooling
branch
from
September 2, 2026 10:22
f0b3a46 to
79cde4c
Compare
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
1 participant
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.
Stacked on #453 (review that first — this diff shows only the release-tooling changes).
Implements the release-tooling part of the PubSub package split (PDR-091b):
release.yml: oneworkflow_dispatchreleasesably-pubsub-coreandably-pubsub-serverat the same version via RubyGems trusted publishing (OIDC — no long-lived API keys).= x.y.zcore pin disagree — a partial or skewed release is impossible.rake releaseprocess (and theably-ruby-restrelease step — both legacy gems are maintenance-only under PDR-091b).Not in this PR (deferred admin, tracked in the rollout plan): configuring the Trusted Publishers on rubygems.org for both gems — the workflow will fail until that's done, and the bindings must target the post-rename repo name.
🤖 Generated with Claude Code