Skip to content

Release via npm trusted publishing instead of NPM_TOKEN - #1

Merged
hjk-sys merged 3 commits into
mainfrom
claude/project-thread-vbm460
Nov 10, 2026
Merged

hjk-sys merged 3 commits into
mainfrom
claude/project-thread-vbm460

Conversation

@hjk-sys

@hjk-sys hjk-sys commented Nov 9, 2026 •

Copy link
Copy Markdown
Owner

The release workflow stops using the NPM_TOKEN secret. npm stage publish now authenticates with the workflow's GitHub OIDC identity through a trusted publisher on npmjs.com, and npm adds provenance automatically, so --provenance is dropped. Releases are still staged and need approval on npmjs.com before going live.

The repo was renamed to decompact, and npm requires repository.url in package.json to match the publishing repo exactly, so all links (package.json, plugin manifest, README, share-page footer, test) now point at hjk-sys/decompact.

Before the next tag: configure the trusted publisher for decompact on npmjs.com (user hjk-sys, repo decompact, workflow release.yml, no environment). After the first successful release, delete the NPM_TOKEN secret and set publishing access to disallow tokens.

@hjk-sys hjk-sys self-assigned this Nov 9, 2026
@hjk-sys
hjk-sys merged commit 1784e61 into main Nov 10, 2026
9 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