Skip to content

docs: live CDN now serves 0.3.14 #22

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kdr merged 1 commit into from
Jul 19, 2026
Merged

docs: live CDN now serves 0.3.14 #22

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -214,9 +214,9 @@ of printing JSON. Any script invoking the binary must redirect `</dev/null`
metadata sync) vs live-CDN jobs (`Install + smoke` matrix, npx-against-CDN)
which run only on push to main or manual dispatch — never on PRs, because a
CDN gap would fail every PR.
- The live CDN serves 0.3.13 (latest aliases + v-prefixed pinned tarballs
for 0.3.0 through 0.3.13, with `manifest.json` + `.sha256`
sidecars; `channels.stable` = 0.3.13); all smoke legs are required.
- The live CDN serves 0.3.14 (latest aliases + v-prefixed pinned tarballs
for 0.3.0 through 0.3.14, with `manifest.json` + `.sha256`
sidecars; `channels.stable` = 0.3.14); all smoke legs are required.
- `publish-npm.yml` (tag `v*`): asserts tag == package.json version → gates
on `generate-manifest.mjs --check` against the live CDN → publishes via
npm trusted publishing (OIDC, `id-token: write`, npm ≥ 11.5.1 — no token
Expand Down
Loading