chore: release 0.11.9 (no code changes — refresh @latest + let CI own GH release)#109
Merged
Conversation
…ate GH release) The 0.11.0–0.11.8 Publish workflow runs all showed red, but every npm publish step actually succeeded (the registry has 0.11.0–0.11.6 and 0.11.8 — only 0.11.7 is missing, that one had the ESM postinstall bug). What failed was the FINAL "Create GitHub release" step: I was creating each release manually via `gh release create` before the workflow could, which made it hit `HTTP 422: Release.tag_name already exists` and exit non-zero. This bump is metadata-only — same code as 0.11.8. Goal: 1. Refresh @latest with a clean install signature for users who saw stale install state. 2. Let the Publish workflow run end-to-end without me racing it, so the run shows green and proves the workflow is healthy. 3. From now on no `gh release create` from local — the workflow owns release creation via `--generate-notes`.
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.
Metadata-only bump. The 0.11.0–0.11.8 Publish workflow showed red because I was creating each
gh releasemanually before the workflow could (HTTP 422: Release.tag_name already exists), even though npm publish succeeded each time. This bump triggers a clean end-to-end Publish workflow run with no manual release racing it. From now on the workflow owns release creation via--generate-notes.Summary by cubic
Metadata-only bump to 0.11.9 to refresh
@latestand let the Publish workflow create the GitHub release, preventing tag collisions that made earlier runs look red. Also adds.claude/to.gitignore.Written for commit bf7bf5b. Summary will update on new commits.