Revert "Merge pull request #209 from Usercentrics/release-2.31.0" - #210
Closed
islameldesoky95 wants to merge 1 commit into
Closed
Revert "Merge pull request #209 from Usercentrics/release-2.31.0"#210islameldesoky95 wants to merge 1 commit into
islameldesoky95 wants to merge 1 commit into
Conversation
Contributor
Author
|
Closing — no need to revert. Simpler path: a trivial commit + squash-merge PR titled 'Release: 2.31.0' gives us the right commit message on top of the already-merged content, then we just tag that. |
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.
Reverts the 2.31.0 release merge to redo it via squash-merge with the correct
Release: 2.31.0 (#NNN)commit message, per RELEASE.md's commit convention. The regular merge commit produced by #209 didn't match that format, and pub.dev's automated-publishing tag push (2.31.0) failed with a pub.dev authorization error we're investigating. Re-merging via squash is a cheap, safe thing to try since it costs nothing and gets us back into the documented convention regardless.