Repository navigation
docs(release): require an up-to-date branch before a squash merge - #32
Merged
Merged
Conversation
A squash merge of a branch behind main produces a tree no pull request verified, which stops the release workflow. Say so next to the recovery steps, and run full Verify on a light-paths recovery branch.
Deploying sqlclean with
|
| Latest commit: |
683814d
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://b855f43c.sqlclean.pages.dev |
| Branch Preview URL: | https://docs-release-merge-freshness.sqlclean.pages.dev |
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
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.
Why
#30 was squash-merged while one commit behind
main, so the release basec8ce21fwas a tree no pull request verified. The release workflow's provenance check stopped, and release pull request #31 was closed following this document's recovery steps. This pull request is the up-to-date merge that recovery needs, and it records the cause so it does not repeat.Changes
.github/RELEASING.md: a squash merge of a stale branch breaks the release the same way as back-to-back merges; update the branch and wait for Verify before merging. A light-paths recovery branch also runs Verify byworkflow_dispatch, so the release base gets every suite.No product, workflow or check changes.
Verification
fensu checkreports 0 faults.workflow_dispatchVerify on this branch head that runs every suite against the exact treemainwill hold.