Skip to content

ci: record npm publishes on the Deployments page - #101

Merged
mrjasonroy merged 1 commit into
mainfrom
ci/deployments-env
Nov 3, 2026
Merged

mrjasonroy merged 1 commit into
mainfrom
ci/deployments-env

Conversation

@mrjasonroy

Copy link
Copy Markdown
Owner

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.

  • `publish.yml`: the publish job runs in an `npm` environment, with its URL set to the published version on npmjs.com. The dist-tag step also outputs `version` for that URL.
  • No protection rules, so the daily auto-publish stays ungated.
  • npm trusted publishing: the job already publishes with no environment, so the trusted publisher config does not pin one, and adding one doesn't break OIDC.

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

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
mrjasonroy merged commit 094f1cd into main Nov 3, 2026
16 checks passed
@mrjasonroy
mrjasonroy deleted the ci/deployments-env branch November 3, 2026 18:05
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