chore(release): restore 2.19.2 for clean release retry#292
Merged
Conversation
Deploying podnotes with
|
| Latest commit: |
ec3032d
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://527c715a.podnotes.pages.dev |
| Branch Preview URL: | https://chore-recover-release-2-19-3.podnotes.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
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.
Restore the four synchronized version files to the last published release, 2.19.2.\n\nThe first 2.19.3 release PR was merged with a custom squash subject that omitted the required PR-number suffix. The forensic release trigger correctly refused to publish it. Rolling back the unpublished version bump lets the existing release planner generate a fresh 2.19.3 PR with new provenance, without weakening validation or rewriting master.\n\nAfter this merges, Prepare release will be dispatched again and the regenerated release PR will use GitHub's default squash subject.