fix(ci): publish the TypeScript SDK for v0.7.0 - #134
Merged
Conversation
The v0.7.0 tag's TypeScript SDK publish failed because package.json was still at 0.6.0 — the version guard correctly refused to publish a mismatched version. Bump package.json (and the package-lock version fields) to 0.7.0 so the package matches the release. Also add a workflow_dispatch trigger to the publish workflow and skip the tag-match guard on a manual run, so an SDK that shipped before its version was bumped can be re-published from a branch without re-tagging the whole release. Publishing stays idempotent (it skips a version already on npm).
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 v0.7.0
Publish TypeScript SDKrun failed withtag v0.7.0 does not match package.json version 0.6.0—sdks/typescript/package.jsonwasn't bumped in the release PR, and the workflow's version guard correctly refused to publish a mismatched version. (The Go release and the Python SDK publish both succeeded; only the TS SDK is missing from npm.)This:
sdks/typescript/package.jsonand the twopackage-lock.jsonversion fields to 0.7.0 (surgical edits — no dependency re-resolution;npm cistays consistent, 0 vulnerabilities).workflow_dispatchtrigger totypescript-publish.ymland skips the tag-match guard on a manual run, so the SDK can be re-published from a branch without re-tagging the whole release. Publishing stays idempotent (skips a version already on npm).After merge I'll run the publish workflow from
mainto push@riskkernel/sdk@0.7.0, leaving the already-published, signed Go release and the Python SDK untouched.Verified locally:
npm ci+npm run typecheck+npm test+npm run buildall pass;npm auditreports 0 vulnerabilities.