Automate release of Windows installer. #1999
Merged
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.
Summary
This automates signing the Windows installer and attaching it to the releases. Windows installers built via AppVeyor will now have an
-unsigned
suffix in their filenames, and the code that signs the installer will remove the suffix after signing it. This signing code is running on the same server that's handling hosting the nightly builds.This might need a bit of hand-holding / monitoring for the very next release we do, to ensure that everything works as expected. cc @bestander
Once we ensure this is working, we can automate bumping the
latest_release
config field on the website, and the release process will be fully automated! 🎉Test plan
Played around with it in my fork, manually called the webhook with a valid AppVeyor payload and ensured it worked (https://github.com/Daniel15/yarn/releases/tag/v0.18.0-0)
Closes #1977