Select the newest published development build explicitly - #79
Merged
Conversation
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
1 participant
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 public graphical install check caught GitHub returning the older development release first. The bootstrap selected that first match, installing an old app without Setup. Select the maximum published_at among eligible complete development releases instead of trusting collection order.
A regression test covers both API orders. The public install/update job also asserts the installed source commit, so a wrong build cannot pass simply because doctor is ready.
Validation: all four release-selection/update tests and shell syntax pass locally. This fixes the download path used by both graphical Setup and the installed CLI updater.