Skip to content

Commit

Permalink
docs(NODE-6238): update release integrity section
Browse files Browse the repository at this point in the history
  • Loading branch information
durran committed Jun 27, 2024
1 parent 7d1c1d4 commit 5fa0036
Showing 1 changed file with 10 additions and 0 deletions.
10 changes: 10 additions & 0 deletions readme.md
Original file line number Diff line number Diff line change
Expand Up @@ -65,6 +65,12 @@ npm install mongodb-legacy

### Release Integrity

Releases are created automatically and signed using the [Node team's GPG key](https://pgp.mongodb.com/node-driver.asc). This applies to the git tag as well as all release packages provided as part of a GitHub release. To verify the provided packages, download the key and import it using gpg:

```
gpg --import node-driver.asc
```

The GitHub release contains a detached signature file for the NPM package (named
`mongodb-legacy-X.Y.Z.tgz.sig`).

Expand All @@ -78,6 +84,10 @@ Using the result of the above command, a `curl` command can return the official
To verify the integrity of the downloaded package, run the following command:
```shell
gpg --verify mongodb-legacy-X.Y.Z.tgz.sig mongodb-legacy-X.Y.Z.tgz

>[!Note]
No verification is done when using npm to install the package. To ensure release integrity when using npm, download the tarball manually from the GitHub release, verify the signature, then install the package from the downloaded tarball using `npm install mongodb-legacy-X.Y.Z.tgz`.

```

### Versioning
Expand Down

0 comments on commit 5fa0036

Please sign in to comment.