chore(release): bump jsr.json to v1.1.0 for JSR publish#151
Merged
Conversation
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.
Follow-up: bump
jsr.jsonto v1.1.0 (JSR publish)The TS SDK release (#150) bumped
sdks/typescript/package.json→ npm published1.1.0✓, butsdks/typescript/jsr.jsoncarries its ownversionfield which I missed — it stayed at1.0.5. Thesdk-typescript.ymlJSR step reads the version fromjsr.json, saw1.0.5already on JSR, and skipped (gracefully — that's why the run was green). So JSR is still at 1.0.5 while npm is at 1.1.0.This bumps
jsr.json→1.1.0. On merge,sdk-typescript.ymlre-runs and its JSR step (npx jsr publishvia OIDC) detects1.1.0as new and publishes it; the npm step skips (1.1.0 already published).vp checkgreen. Onlysdks/typescript/jsr.jsonchanged.