Repository navigation
chore(ci): confirm the release is the latest one before the job ends - #3
Merged
Merged
Conversation
The release is created published, so the pointer normally moves on its own. That is not guaranteed, though: publishing a draft does not make GitHub recompute which release is the latest one, and that is exactly what happened on rclone-deck with v0.1.1 — the release looked published, the pointer still pointed at the previous version, and the updater endpoint answered 404, so no installed app was ever offered the new build. The step every other release path in this account now ends with does three things: publish the release, mark it as the latest one, and read the API back to confirm the pointer moved. A mismatch fails the job instead of leaving the update feed on the old version.
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 release is created published, so the pointer normally moves on its own. That is not guaranteed, though: publishing a draft does not make GitHub recompute which release is the latest one, and that is exactly what happened on rclone-deck with v0.1.1 — the release looked published, the pointer still pointed at the previous version, and the updater endpoint answered 404, so no installed app was ever offered the new build.
The step every other release path in this account now ends with does three things: publish the release, mark it as the latest one, and read the API back to confirm the pointer moved. A mismatch fails the job instead of leaving the update feed on the old version.