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.

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

docs(NODE-6238): update release integrity section #41

Merged
merged 4 commits into from
Jun 27, 2024
Merged
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
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

W-A-James marked this conversation as resolved.
Show resolved Hide resolved
>[!Note]
durran marked this conversation as resolved.
Show resolved Hide resolved
No verification is done when using npm to install the package. The contents of the Github tarball and npm's tarball are identical.

```

### Versioning
Expand Down