chore: adding script for initial npm publish#1216
Conversation
|
@launchdarkly/js-sdk-common size report |
|
@launchdarkly/js-client-sdk size report |
|
@launchdarkly/browser size report |
|
@launchdarkly/js-client-sdk-common size report |
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
|
@cursor review |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
|
@cursor review |
contributing/publishing.md
Outdated
| to configure trusted publishing on the new NPM package, then mark the package public. | ||
|
|
||
| After everything is set up, you can then mark the package public. | ||
| > HINT: you will need to enable the `release-please.yml` workflow for |
There was a problem hiding this comment.
I'll make it more obvious 👍
2 participants
Creating a more scripted flow for initial package publishing to set up npm OIDC
Note
Low Risk
Low risk documentation and tooling change; the new script can publish to npm and relies on user credentials, but it is an explicit manual step with safeguards to skip existing packages.
Overview
Streamlines initial npm package bootstrapping for OIDC trusted publishing by replacing the manual placeholder publish steps in
contributing/publishing.mdwith a single./scripts/publish-placeholder-package.shcommand and repo-specific trusted-publisher values.Adds
publish-placeholder-package.sh, which derives the package name from a workspace path, checks npm to avoid publishing if the package already exists, and publishes an empty0.0.0placeholder under thesnapshottag while handlingnpm login/npm logoutand cleanup automatically.Written by Cursor Bugbot for commit 488370a. This will update automatically on new commits. Configure here.