Repository navigation
chore: allow first npm publish with provenance from Actions - #119
Merged
Merged
Conversation
Add publishConfig.access=public so new packages can publish with provenance, and workflow_dispatch so we can re-run bin/publish after a partial release without cutting another release-please version. Co-authored-by: Cursor <cursoragent@cursor.com>
adamlogic
force-pushed
the
adam/publishconfig-public-access
branch
from
August 18, 2026 13:30
5757aa4 to
c5f891e
Compare
adamlogic
changed the title
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit c5f891e. Configure here.
workflow_dispatch can target any branch in the UI; skip the job unless the ref is main. Co-authored-by: Cursor <cursoragent@cursor.com>
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.
Summary
The release of
judoscale-nextjs@2.0.1failed in CI because npm refuses provenance for a new package unless access is explicitly public. Existing packages were fine because they were already on the registry. GitHub already has thev2.0.1release/tag; npm does not.This adds
publishConfig.access: publicto every package and aworkflow_dispatchtrigger on the release workflow so we can re-runbin/publishfrom the fixed commit without cutting another release-please version.Design decisions
chore, notfix— this is release tooling, not a user-facing package bug. Usingfixwould open a release PR and bump every touched package, leaving2.0.1unpublished on npm.publishConfigon all packages — same future-proofing for the next new package name.workflow_dispatch—bin/publishis idempotent (skips versions that exist). After merge, manually run the workflow to finish publishingjudoscale-nextjs@2.0.1with provenance.After merge
workflow_dispatch).npm view judoscale-nextjs versionis2.0.1.Note
Low Risk
CI/release configuration only; no application runtime or auth logic changes.
Overview
Fixes failed first-time npm publishes with provenance by adding
publishConfig.access: "public"to every workspacepackage.json, so npm treats new packages as explicitly public when CI runs withNPM_CONFIG_PROVENANCE.The release-please workflow gains
workflow_dispatch(guarded tomainonly) and the checkout/setup-node/bin/publishsteps now run when a release is created or the workflow is manually triggered, so you can re-run publish after a partial failure without cutting another release-please version.Reviewed by Cursor Bugbot for commit 1c61904. Bugbot is set up for automated code reviews on this repo. Configure here.