Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With those changes, the following files will be generated by the release process; I can also see to make an alias on
latest
to quickly find the most recent public key:https://repo.yarnpkg.com/VERSION/packages/yarnpkg-cli/bin/yarn.js - The actual file.
https://repo.yarnpkg.com/VERSION/packages/yarnpkg-cli/bin/yarn.js.sign - The signature for the file.
https://repo.yarnpkg.com/VERSION/packages/yarnpkg-cli/bin/yarn.pem - The public key used for signing the file. Should be the same from one release to another, mostly here for convenience (it's easy to detect when the key changes).
I used the following commands to generate the private and public keys I added to the repository: