Comparing changes
Open a pull request
- 16 commits
- 257 files changed
- 7 contributors
Commits on Feb 7, 2023
-
chore: move generate matrix script to standalone js file (#6145)
chore: fix generate matrix workflow step
Commits on Feb 8, 2023
-
chore: add timeout for citgm command step (#6149)
This also adds a final step that will always run to set the exit code for the citgm job in the case of the command step timing out during known failures
Commits on Feb 13, 2023
-
feat: add provenance attestation
This adds a new `--provenance` flag to npm for provenance attestation during `npm publish` If set to `true`, npm will detect if it is running in GitHub actions and will generate an appropriate attestation bundle for that environment. The primary work in this PR was done by [@bdehamer](https://github.com/bdehamer), with some cleanup and edge-case handling added by the npm cli team.
-
fix: refactor error reporting in audit command
Primary work authored by [@wraithgar](https://github.com/wraithgar).
Commits on Feb 14, 2023
-
fix: gracefully fallback from auth-type=web (#6158)
Originally `auth-type=web` would gracefully fallback to `auth-type=legacy` if a registry had not yet implemented web. This brings back that behavior.
-
Signed-off-by: Philip Harrison <philip@mailharrison.com>
-
feat: audit signatures verifies attestations
Update `audit signatures` to also verify Sigstore attestations. Additional changes: - Adding error message to json error output as there are a lot of different failure cases with signature verification that would be hard to debug without this - Adding predicateType to json error output for attestations to diffentiate between provenance and publish attestations References: - Pacote changes: npm/pacote#259 - RFC: npm/rfcs#626 Signed-off-by: Philip Harrison <philip@mailharrison.com>
-
-
-
-
-
fix: use npmFetch() instead of npmFetch.json() for team destroy comma…
…nd (#6161) The registry returns a 204 status and an empty body on success for the team destroy command. Using npmFetch.json() makes the CLI error out on completion even though the action was completed successfully in the registry.
Commits on Feb 15, 2023
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v9.4.2...v9.5.0