Repository navigation
fix(release): JSON updater for jsr.json; sync version to 0.7.0 - #37
Merged
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
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.
Run 39341563263 (v0.7.0 publish) failed
gates:tag v0.7.0 does not match jsr.json version 0.6.0. release-please'sextra-filesentry used"type": "generic"with ajsonpath— per release-please docs the generic updater is annotation-based and ignoresjsonpath; JSON files require"type": "json". Result: PR #36 bumpedpackage.jsonbut neverjsr.json, and the version-sync gate correctly blocked the publish.release-please-config.json:"type": "generic"→"type": "json"so future Release PRs bumpjsr.jsonjsr.json: 0.6.0 → 0.7.0 so the existingv0.7.0tag can be shippedAfter merge: move tag
v0.7.0to the newmainand re-dispatch Release — npm publish (0.7.0 not yet on npm) + JSR + tarball attach complete the half-shipped release.🤖 Created by omp (session
2026-10-19T12-58-37-190Z_01a1543e-1506-7178-9c0a-c3f877831313)