Symptom
The publish-commit job in ci.yml fails on every push to main with:
``` Publishing @stacksjs/bunpress... Tarball: 165306 bytes Upload error: {"error":"Invalid token"} ✗ Failed Publishing bun-plugin-bunpress... Tarball: 2273 bytes Upload error: {"error":"Invalid token"} ✗ Failed
✗ 2 package(s) failed ##[error]Process completed with exit code 1. ```
Latest failed run: https://github.com/stacksjs/bunpress/actions/runs/25434766639
Why this only just surfaced
Until 12f89c7, the test job was failing first and publish-commit was being skipped (job dependency). With test/typecheck/lint all green, publish-commit now runs and exposes a pre-existing secret problem. Same shape as a token rotation that already cleared up stacksjs/gitlint earlier this week — its publish-commit runs are succeeding again.
Fix
Rotate the PANTRY_REGISTRY_TOKEN repo secret on stacksjs/bunpress:
- Generate a fresh token from registry.pantry.dev (admin)
- Update
Settings → Secrets and variables → Actions → PANTRY_REGISTRY_TOKENon this repo - Re-run the failed workflow (or push any commit) to verify
No code change needed.
Acceptance
publish-commitjob goes green on the next CI run@stacksjs/bunpressandbun-plugin-bunpressare reachable on registry.pantry.dev at the published commit version