chore(release): force 1.0.2 to ship release-please-action v5.0.0-oce.3 - #30
Closed
kojiromike wants to merge 1 commit into
Closed
chore(release): force 1.0.2 to ship release-please-action v5.0.0-oce.3#30kojiromike wants to merge 1 commit into
kojiromike wants to merge 1 commit into
Conversation
Tag 1.0.1 was cut about three minutes before #28 merged, so it still pins release-please-action v5.0.0-oce.2, the opt-in annotated-tag build. #28 landed as a ci: commit, which this config marks hidden and non-releasing, so release-please will not open a release PR on its own. An empty Release-As commit (#29) squash-merged to nothing. Set release-as so the next release-please run cuts 1.0.2 carrying the oce.3 pin. Remove this key once 1.0.2 is tagged. Assisted-by: Claude Code
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.
One-line config change:
"release-as": "1.0.2"inrelease-please-config.json.Tag
1.0.1was cut about three minutes before #28 merged, so it still pinsrelease-please-action@v5.0.0-oce.2, the opt-in annotated-tag build. #28 landed as aci:commit, which this config marks hidden and non-releasing, so no release PR opens on its own. #29 tried an emptyRelease-Ascommit, which squash-merged to nothing.release-asis the documented manifest-mode mechanism for forcing a version. It is a real diff, so squash cannot drop it. Once1.0.2is tagged, a follow-up PR removes the key; leaving it in place would make release-please try to release1.0.2again.After merging: approve and merge the
chore(main): release 1.0.2PR that release-please opens. Dependabot then moves the 26 reusable-workflow consumers to the tag that carriesoce.3.