🐸 Versioned release#8
Merged
Merged
Conversation
fledgling@1.2.0
bumpy-bot
force-pushed
the
bumpy/version-packages
branch
from
July 15, 2026 00:42
7cee215 to
ed25ea8
Compare
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
2 participants
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.
This PR was created and will be kept in sync by bumpy based on your bump files (in
.bumpy/). Merge it when you are ready to release the packages listed below:fledgling1.1.1 → 1.2.0 CHANGELOG.mdfledgling jsrcommand — the same first-publish story, on JSR. Scaffolds missingjsr.jsonmanifests frompackage.json, claims each package on jsr.io (JSR has no create-on-first-publish), links your GitHub repo so CI publishes token-lessly via OIDC (npx jsr publish, noJSR_TOKENsecret), and syncs the score metadata JSR only stores server-side — package description (frompackage.json) and runtime compatibility (fromfledgling.jsr.runtimeCompatconfig). Idempotent (reconciles metadata drift on every run), rate-limit aware, and stops cleanly at JSR's 20-new-packages-per-week scope quota. Auth via a full-access JSR token in$JSR_TOKEN; configure a default scope for unscoped packages withfledgling.jsr.scope. Thanks to @Saeris for the proposal and reference implementation this is built on. (bump file)@gunshi/plugin-completion(replacing the hand-rolled@bomb.sh/tabintegration). Completion behaves the same — package names,--provider, and--permissionsstill complete — and thepackagesargument is now documented in--help. (bump file)