fix: set npm version from the GitHub Release tag - #5
Merged
Merged
Conversation
The v26.9.2 publish failed because package.json still said 26.9.1. Match ocInsights: the release tag is the source of truth, overwrite package.json at publish time, and use dist-tag next for prereleases.
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.
The
v26.9.2publish failed because the workflow requiredpackage.jsonto already match the tag (26.9.1vsv26.9.2). This matches ocInsights: a GitHub Release is the source of truth, and the workflow overwritespackage.jsonversionfrom the tag before pack/publish.release: published(a tag push alone does nothing)vYY.M.patch(optional-prerelease) viascripts/releaseVersion.tsnextfor GitHub prereleases or a-suffixversion; otherwiselatestpackage.jsonat the last published version (26.9.1); do not bump it for a releaseAfter merge, cut a new GitHub Release (
v26.9.3). Re-running the failed job would reuse the old commit and the old workflow. The existingv26.9.2tag/release can be deleted later if you want; it never reached npm.Models: xai/grok-4.6:default, anthropic/claude-fable-5-1:xhigh