Add npm provenance to secure releases (#877)

* feat: add npm provenance to releases * feat: add npm provenance to releases
belgattitude · Jan 6, 2024 · e329bcd · e329bcd
1 parent a448ce6
commit e329bcd
Show file tree

Hide file tree

Showing 2 changed files with 10 additions and 0 deletions.
diff --git a/.changeset/eleven-cherries-raise.md b/.changeset/eleven-cherries-raise.md
@@ -0,0 +1,9 @@
+---
+"prisma-exception": patch
+"@httpx/assert": patch
+"@httpx/dsn-parser": patch
+"@httpx/exception": patch
+"@httpx/json-api": patch
+---
+
+Add npm provenance to releases
diff --git a/.github/workflows/release-or-version-pr.yml b/.github/workflows/release-or-version-pr.yml
@@ -53,4 +53,5 @@ jobs:
           # trigger the regular CI workflow. This limitation can be circumvented by
           # setting a custom PAT token from a GH account and setting it the secrets.
           GITHUB_TOKEN: ${{ secrets.BELGATTITUDE_HTTPX_TOKEN }}
+          NPM_CONFIG_PROVENANCE: true