Resume and refresh release preparation safely - #14
Merged
Merged
Conversation
samuel-williams-shopify
force-pushed
the
refresh-release-preparation
branch
2 times, most recently
from
September 21, 2026 20:48
8d5ed3e to
3045973
Compare
samuel-williams-shopify
force-pushed
the
refresh-release-preparation
branch
from
September 21, 2026 21:26
3045973 to
355ce52
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.
Preparation validates and reuses an existing local or remote release branch, so retrying after an interrupted push or PR creation does not create another version bump. Existing PRs are validated against the current default branch; stale content and conflicting release requests stop.
Adds
refresh=trueto the release tasks and preparation workflow. Refresh preserves the previous commit, including manual edits, underrelease-backups/vVERSION/OLD_SHA, regenerates from the current default branch, and updates the release branch with an explicit force-with-lease. Concurrent remote updates are rejected. The shared guide and generated agent context explain retrying and refreshing.Validation: 90 tests / 273 assertions pass, with 378/378 measured lines covered. RuboCop and API documentation coverage pass. Tests use real Git repositories and Bake tasks for interrupted PR creation, unpublished local branches, stale notes, manual edits, concurrent pushes, and conflicting requests.