chore: reconcile the release manifest with what is published - #18
Merged
Conversation
release-please tracks the last version it released. These releases were cut by hand while a chain of ceilings was being widened, so its manifest stayed behind and it kept proposing a version that already exists on the registry — a release PR that could never be merged and quietly aged. The manifest is moved to the published tag. The next proposal starts from where the world actually is.
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.
release-please's manifest lagged behind hand-cut releases, so PR #15 proposes a version that already exists. Moving the manifest to the published tag lets the next proposal start from reality.
Greenhouse cleanup,
evidence/0181.