Skip to content

fix: Rotate NPM_TOKEN and publish v0.4.0 to npm #49

@dean0x

Description

@dean0x

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.

  1. Rotate the npm token on npmjs.com
  2. Update the NPM_TOKEN GitHub Actions secret with the new token
  3. Re-trigger the CI workflow on main (or push a no-op commit)
  4. Verify v0.4.0 appears on https://www.npmjs.com/package/claudine

Acceptance Criteria

  • npm info claudine version returns 0.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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workinglaunch-blockerBlocks public launch readinesspriority:highHigh priority

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions