Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

chore: publish to NPM with provenance #5835

Merged
merged 3 commits into from Nov 8, 2023
Merged

chore: publish to NPM with provenance #5835

merged 3 commits into from Nov 8, 2023

Commits on Aug 26, 2023

  1. chore: Publish to NPM with provenance 

    The release process in this repository is already automated via
GitHub Actions, which is a great first step toward creating trust in the
supply chain. Recently, NPM has started to support publishing with the
`--provenance` flag. This flag creates a link between the GitHub Actions
run that created the release and the final artifact on NPM. This linkage
further ensures that package installs can be traced back to a specific
code revision.

For more information on publishing with provenance, please refer to:
https://github.blog/2023-04-19-introducing-npm-package-provenance/
    @meyfa
    meyfa committed Aug 26, 2023
    Configuration menu
    Copy the full SHA
    7ded7aa View commit details
    Browse the repository at this point in the history

Commits on Aug 30, 2023

  1. Merge branch 'v1.x' into patch-1

    @jasonsaayman
    jasonsaayman committed Aug 30, 2023
    Configuration menu
    Copy the full SHA
    46f4768 View commit details
    Browse the repository at this point in the history

Commits on Nov 8, 2023

  1. Merge branch 'v1.x' into patch-1

    @DigitalBrainJS
    DigitalBrainJS committed Nov 8, 2023
    Configuration menu
    Copy the full SHA
    f165e9c View commit details
    Browse the repository at this point in the history