Skip to content

fix(release): re-enable JSR settings applyOnPublish (new beta.6 packages lack descriptions)#616

Merged
rickylabs merged 2 commits into
mainfrom
fix/jsr-settings-apply-on-publish
Jul 11, 2026
Merged

fix(release): re-enable JSR settings applyOnPublish (new beta.6 packages lack descriptions)#616
rickylabs merged 2 commits into
mainfrom
fix/jsr-settings-apply-on-publish

Conversation

@rickylabs

Copy link
Copy Markdown
Owner

Summary

jsr-package-settings.json had applyOnPublish: false (set when the pre-existing package settings had stabilized), so the beta.6 publish skipped the "Apply JSR package settings" step — and this cut introduced three first-time-published packages (@netscript/ai, @netscript/plugin-ai-core, plugin-ai) which now sit on JSR with no description/readmeSource/runtimeCompat. The refreshed README taglines from the #610 doc pass (telemetry + core packages) also never synced. Local read-only reconciler run confirms 11 pending diffs.

Flips the flag back to true. The reconciler is idempotent (separate PATCH per changed field, no-op when unchanged), so keeping it on costs nothing on quiet releases and covers every future new package automatically.

After merge

Re-dispatch publish.yml (workflow_dispatch, tag v0.0.1-beta.6): republish is a no-op for already-published members and the settings step then reconciles the 11 pending diffs.

Spotted by the owner on jsr.io/@netscript (ai card missing its description). Refs #609.

rickylabs and others added 2 commits July 11, 2026 10:39
…core, plugin-ai) published without JSR descriptions

The settings reconciler was switched off after the existing package settings
stabilized, so the beta.6 first-publish of the ai packages landed with no
description/readmeSource/runtimeCompat, and the refreshed README taglines from
the beta.6 doc pass never synced. The step is idempotent per-field PATCH, so
keeping it on is safe.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WVCH2JZKKMDJU3A7jxDxPo
…e jsr-settings workflow

- publish.yml settings step is now explicitly non-critical: --best-effort exit-0
  semantics plus continue-on-error, so a settings/API mismatch can never red a
  run whose JSR publish succeeded.
- New jsr-settings.yml workflow_dispatch reconciles on demand, all members or a
  single --package, with a dry-run toggle.
@rickylabs
rickylabs merged commit 71b36d8 into main Jul 11, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant