Repository navigation
ci: record npm publishes on the Deployments page - #101
Merged
Merged
Conversation
The publish job now runs in an "npm" environment whose URL is the published version on npmjs.com, so each release shows up under the repo's Deployments. The environment has no protection rules, so the automated publish is not gated. npm trusted publishing is unaffected: it already publishes without an environment, so the trusted publisher config does not pin one. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
mrjasonroy
force-pushed
the
ci/deployments-env
branch
from
November 3, 2026 17:50
9b9dad8 to
1f9b2f3
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
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.
The repo's Deployments page is empty because no workflow job declares an `environment`. The publish job had `environment: publish` commented out, on the assumption that an environment means a manual approval gate. It only does if the environment has protection rules.
Releases from now on appear under Deployments. Earlier releases won't. The unused `publish` and `publishing` environments can be deleted separately.
🤖 Generated with Claude Code