chore: sync the release manifest with the tags that actually exist - #14
Merged
Conversation
The manifest said 0.1.6 while the repository is tagged up to v0.2.1. Since that file is the only thing release-please reads to decide the next version, its open release PR proposed a version OLDER than what is published — recreating an existing tag at best, and at worst offering composer a version below the installed one, so the work would never reach an app. One metadata file, no source. A chore on purpose: this must not bump anything by itself.
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-pleasehas not been governing this repository since its manifest was last touched, and its manifest is the only thing it reads to decide the next version.Everything between those two was tagged by another route, so the release PR release-please keeps open proposes a version older than what is already published. Merging it would try to recreate a tag that exists, and if it ever succeeded, composer would see a version below the installed one — the change would never reach an app. A published contract that cannot be reached is a defect this house has already paid for once (greenhouse
evidence/0179).This sets the manifest to the version that actually exists, so the next release PR proposes the real next one instead of walking backwards. It changes one metadata file, no source, and it is a
choreon purpose: it must not itself produce a version bump.Part of a family-wide sweep — 24 of 35 repositories were drifted, measured against the remotes rather than local checkouts.