feat: reusable npm-publish.yml with trusted publishing (OIDC) - #1
Open
beel-it wants to merge 2 commits into
Open
feat: reusable npm-publish.yml with trusted publishing (OIDC)#1beel-it wants to merge 2 commits into
beel-it wants to merge 2 commits into
Conversation
… idempotente; el composite queda deprecado
…ate the token-based composite
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.
What
.github/workflows/npm-publish.yml: publishes one or more npm packages from the calling ref with trusted publishing (OIDC) and provenance, after averifyscript passes, behind a GitHub environment with required reviewers.require-tagchecksv<version>= package.json) and monorepos (packages: a b).npm-publishcomposite is documented as deprecated (long-lived token, automatic bumps, continues on failing tests). Kept for existing references.Why
Every npm package of the organization publishes in a slightly different way. This generalizes the pattern already used by
beel-mcpso each repository only keeps a ten-line caller workflow, and no repository needs an npm token.Tests
Workflow linted with actionlint locally. First consumer to follow in a separate repository.
🤖 Generated with Claude Code