Repository navigation
ci: keep the library's release marked Latest - #789
Merged
Merged
Conversation
When the library and sqlstore release together, release-please creates sqlstore's release a second after the library's, and GitHub marks the newest release Latest. Mark the library's release Latest after any release of it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
5 tasks done
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
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.
Summary
When the library and sqlstore release together, release-please creates sqlstore's release a second after the library's. GitHub then marks the sqlstore release Latest, which happened with v0.57.1 / sqlstore v0.1.0 and with v0.58.0 / sqlstore v0.2.0. So the repository page and
/releases/latestpointed at the SQL store module.The release-please step now has an id. When it creates a library release (the root path's
release_createdoutput), a new step runsgh release edit "$TAG" --latestwith the job's token, which already hascontents: write. The tag reaches the shell throughenv, not interpolated into the script.Test plan
.sets the unprefixedrelease_createdandtag_nameoutputs.gh release edit v0.58.0 --latestby hand; v0.58.0 is now Latest.🤖 Generated with Claude Code