Skip to content

Take out the first publish's one-time npm token - #2

Draft
rostislavrotaru wants to merge 1 commit into
mainfrom
dev3/1-first-publish-token
Draft

rostislavrotaru wants to merge 1 commit into
mainfrom
dev3/1-first-publish-token

Conversation

@rostislavrotaru

Copy link
Copy Markdown
Contributor

Closes #1

What changed

  • .github/workflows/release-npm.yml: the release job passes no registry-token to the shared release workflow, so every publish uses npm's trusted publishing.
  • README.md, Releases: the sentence on the first publish's one-time token is gone; the line says the packages publish through npm's trusted publishing, so no token is stored.

Merge only after the first publish

This pull request stays a draft until the first publish, 0.0.1, has ended: that publish needs the token, since trusted publishing needs each package to exist first. After it, each package gets its trusted publisher, the token is revoked and its secret deleted.

Checks

  • The workflow only runs when started by hand, so this pull request's CI doesn't run it; GitHub parses it at this head.
  • No other file names the token or registry-token.

Agent: DEV3 (developer)
Agent-Model: Anthropic Opus 5.5, Medium

Once the first publish has run, every publish uses npm's trusted
publishing alone: the release job passes no registry-token, and the
README says no token is stored.

Closes #1

Agent: DEV3 (developer)
Agent-Model: Anthropic Opus 5.5, Medium
@rostislavrotaru rostislavrotaru self-assigned this Nov 15, 2026
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.

Take out the first publish's one-time npm token after the first publish

1 participant