Setup staged publication#1568
Merged
Merged
Conversation
acoburn
approved these changes
Jun 16, 2026
Enforces an operator intervention (gated by 2FA) to publish the package after the automated CI staged it. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
NSeydoux
force-pushed
the
ci/staged-npm-publication
branch
from
6086f31 to
a2afd25
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Enforces an operator intervention (gated by 2FA) to publish the package after the automated CI staged it.
This mirrors the change made in
solid-client-errors-js(inrupt/solid-client-errors-js#619): the release workflow now runsnpm stage publishinstead ofnpm publish, so a human must complete publication on npmjs.com.🤖 Generated with Claude Code