Repository navigation
quest: finish jsr-retire, every @moq JSR package is archived - #8216
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 15 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. |
kixelated
left a comment
kixelated
left a comment
There was a problem hiding this comment.
Automated review by review (OpenAI)
Reviewed 9ab99c9.
No actionable findings in this documentation cleanup. Removing the completed quest and replacing its dependent links with the retirement outcome is consistent with the npm-only release path. The prerequisite release backport (#8119) is merged, and the inspected release scripts no longer publish to JSR.
Verification limits: GitHub-only static review of all four changed files, the merged backport and main/release publishing scripts. I did not independently verify the external registry's 15 archive states, descriptions or OIDC-link removal; those remain author-reported. No tests or quest validation run. Rechecked open/non-draft state, full head/base and published reviews immediately before posting.
![pullfrog[bot]](https://avatars.githubusercontent.com/in/1768019?s=60&v=4){kind=small}
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes
Reviewed the full 4-file diff at 9ab99c9 and independently verified its claims: the JSR scope API reports zero unarchived packages and all 15 @moq packages report isArchived: true with the "Moved to npm" description, and origin/release has no deno publish, JSR_TOKEN, or jsr.json remaining (backport #8119 merged).
- Deleted
quest/m0/ci/jsr-retire.md— the quest is done, so removing it (rather than leaving a completed quest in the tree) matches how earlier quests were retired. quest/m0/ci/README.md— only the## Requiredline for the deleted quest is removed; no other JSR text remains in the milestone docs.quest/m0/ci/read-only-secrets.md— the JSR decision now records the outcome (publishing gone frommainandrelease, packages archived 2026-11-07, OIDC trust ended) and drops the now-dangling## Relatedlink.quest/m3/release/npm-first-publish.md— the "JSR is dropped" decision now cites the archival instead of the deleted quest.
No remaining jsr-retire links exist anywhere in the tree, and no quest, pipeline, or package metadata is left pointing at JSR.
deepseek-v4.1-flash-1017 (free via Pullfrog for OSS) ｜ 𝕏
Deletes
quest/m0/ci/jsr-retire.md. Its last wait cleared on 2026-11-07: the maintainer approved (in/quest-unblock) an agent driving their logged-in Chrome to archive the packages. All 15@moqpackages (auth, binary, boy, flate, hang, json, loc, msf, net, pattern, publish, room, signals, token, watch) now have the descriptionMoved to npm: https://www.npmjs.com/package/@moq/<name>and are archived.Verified:
curl -s https://api.jsr.io/scopes/moq/packages | jq '[.items[] | select(.isArchived | not) | .name]'prints[], andhttps://api.jsr.io/scopes/moq/packages/<name>reportsisArchived: truefor each of the 15.The two quests that linked it (
m0/ci/read-only-secrets.md,m3/release/npm-first-publish.md) now state the outcome instead of linking it.Public API: none. Wire: none.
Models
Size: XS
Implementer: Claude Code, claude-opus-5-5, high effort
Review
Skipped: a quest deletion with two one-sentence link rewrites, too trivial to need one (Claude Opus 5.5).
🤖 Generated with Claude Code
(Written by Claude Opus 5.5 with high effort)