-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Labels
bugSomething isn't workingSomething isn't workinglaunch-blockerBlocks public launch readinessBlocks public launch readinesspriority:highHigh priorityHigh priority
Description
Problem
CI run 22244296002 on main fails at the npm publish step because the NPM_TOKEN GitHub secret has expired. Users installing claudine from npm get v0.3.3 (Dec 2025) instead of v0.4.0 which has been merged to main.
Scope
Ops task — no code changes required.
- Rotate the npm token on npmjs.com
- Update the
NPM_TOKENGitHub Actions secret with the new token - Re-trigger the CI workflow on
main(or push a no-op commit) - Verify v0.4.0 appears on https://www.npmjs.com/package/claudine
Acceptance Criteria
-
npm info claudine versionreturns0.4.0 - CI publish step passes on
main - New token has appropriate expiry (recommend 1 year)
Dependencies
None — this is the first issue to resolve.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workinglaunch-blockerBlocks public launch readinessBlocks public launch readinesspriority:highHigh priorityHigh priority