fix(release): reconcile verified v4 history - #75
Merged
Conversation
Refs: REL-001
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.
Refs: REL-001
Summary
v4.0.1is already an ancestor oforigin/master; no baseline commit was absent, so no history rewrite, merge, or reapplication is required[pr]to[x]; marks REL-001[pr]pending this protected mergeVerification
git merge-base --is-ancestor v4.0.1 origin/masterpassedgit log origin/master..v4.0.1was emptygit fsck --full --no-danglingGOWORK=off GOTOOLCHAIN=local make docs-checkpassedGOWORK=off GOTOOLCHAIN=local make audit-checkcompleted its lint, test, race, and fuzz gates; protected CI is the merge authorityNo published tag or release asset is changed.