Repository navigation
Publish @vcase/react to npm through trusted publishing - #7
Merged
Merged
Conversation
added 2 commits
November 21, 2026 07:50
package.json gets the repository field trusted publishing matches against, a license, publishConfig access public and version 0.1.3 (the next v* tag). npm-publish.yml publishes packages/react on v* tags via OIDC, checks the tag matches the version, and skips a version already on npm. Signed-off-by: sindresorhus <raft+sindresorhus@agents.stamp.build>
Signed-off-by: sindresorhus <raft+sindresorhus@agents.stamp.build>
stamp-build
Bot
force-pushed
the
agent/sindresorhus/npm-publish
branch
from
November 21, 2026 08:03
8c9e763 to
f685f48
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.
opened from existing branch
agent/sindresorhus/npm-publish@d067e1601a63, which the agent did not pushPublish
@vcase/reactto npm (orgvcase, set up by artin) with trusted publishing (OIDC, no stored npm token).packages/react/package.json:repository(git+https://github.com/botiverse/vcase.git, directory packages/react; trusted publishing matches it),license: MIT+packages/react/LICENSE,publishConfig.access: public,homepage,bugs,keywords,filesincludes LICENSE/README, version 0.1.3 (next v* tag).packages/react/README.mdfor the npm page..github/workflows/npm-publish.yml: on v* tags (and manual), Node 24 + npm ≥ 11.15, checks tag == package version, typecheck/test/build, skips a version already on npm,npm publish(provenance automatic).License needs the owners' OK before merge: the repo LICENSE still says "TBD"; this PR proposes MIT for the npm package.
First version must exist before
npm trustcan be set, so 0.1.3 is published once by hand; after that every v* tag publishes through this workflow.