You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
build: modfying publish action to use npm cli to include provenance in npm publish (#319)
**Requirements**
- [ ] I have added test coverage for new or changed functionality
- [ ] I have followed the repository's [pull request submission
guidelines](../blob/main/CONTRIBUTING.md#submitting-pull-requests)
- [ ] I have validated my changes against all supported platform
versions
**Related issues**
**Describe the solution you've provided**
Yarn publish doesn't currently support NPM's publish package with
provenance functionality. As a workaround until this is supported, we'll
pack the workspace with yarn in order to guarantee we get the same
package as before, and then use the npm cli to do the final publish with
provenance. This also involves passing the workspace path as input
parameters to the publish actions/script as npm's workspace
functionality doesn't work exactly the same as yarns.
While npm's generated provenance isn't the most robust provenance
attestation, it results in a verified checkmark on the npm package page,
which brings the provenance closest to the consumer and makes it most
useful.
**Describe alternatives you've considered**
Ideally we'd want yarn to support this natively, but tracking the yarn
repo issues for the past couple months has shown no movement here.
**Additional context**
Add any other context about the pull request here.
0 commit comments