Automate Windows binary releases on changes to master #646
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.
Second part of #530.
First commit has some general improvements. The improved caching cuts the build time by around half.
Second commit kicks off the workflow on every push to
master
and automatically creates a prerelease with the Windows binary. This release is always calledlatest
and can only exist once. This means the previouslatest
release will be deleted and then re-created with the new Windows binary. The latest release can always be found under the same URL (example https://github.com/FreezyLemon/Av1an/releases/tag/latest).This does not cover full, tagged releases. But those can be made by downloading the last
av1an.exe
and manually attaching it to the release, which makes it easier, I think.