Repository navigation
Recreate the latest release at each master build, so its date and tag are current - #691
Merged
Merged
Conversation
danoli3
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The
latestrelease kept its 16 Oct date and tag:force-branch: truemade EndBug/latest-tag force-push alatestbranch instead of the tag, and moving a tag doesn't change a release's date anyway.latest-releaseworkflow on master pushes: deletes thelatestrelease + tag and creates it again at the pushed commit (dated now). It takes seconds, the builds take minutes before they upload, so their files land in the new releaseBetween the recreate and the first upload
latesthas no files for a few minutes; nightly already skips copying an empty latest.