fix(release): retry missed CLI release - #16
Merged
Merged
Conversation
skapoor8
force-pushed
the
docs/clarify-template-registry-picker
branch
from
September 28, 2026 10:25
c9a2319 to
747a345
Compare
skapoor8
changed the title
skapoor8
marked this pull request as ready for review
September 28, 2026 10:26
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.
Intent
Retry the CLI release that did not start after #15 merged. This PR makes a small README clarification so a new merge can trigger
On Merge.Changes
pm goffers a language-agnostic Default registry.Validation
mise run formatandmise run lintpass.Release note
The earlier
fix(cli)squash commit is already onmain, but GitHub did not schedule itsOn Mergerun. This PR uses afix(release)subject to request a patch release on the next merge. The file change itself only updates documentation. Check the post-merge workflow and release artifacts; a green PR check does not prove that the release ran.