Fix installer latest release selection#299
Merged
github-actions[bot] merged 2 commits intoMay 25, 2026
Merged
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Pull request overview
This PR fixes installer “latest release” selection by avoiding GitHub’s /releases/latest endpoint (which can point to azd extension releases) and instead selecting the newest standalone CLI semver tag, with regression tests and docs updates to match.
Changes:
- Update
install.shandinstall.ps1to scan GitHub releases and pick the first semvervX.Y.Z-style tag. - Add Go regression tests that validate extension releases are skipped and the CLI release tag is chosen.
- Update install documentation to describe “latest standalone CLI release” behavior.
Show a summary per file
| File | Description |
|---|---|
install.sh |
Switches from /releases/latest to scanning releases for a standalone semver tag. |
install.ps1 |
Updates release tag selection logic to filter for semver tags from the releases list. |
install_scripts_test.go |
Adds regression tests for Bash and PowerShell installer release selection. |
README.md |
Clarifies that installers fetch the latest standalone CLI release. |
docs/GUIDE.md |
Updates binary install description to mention standalone CLI release selection. |
site/src/content/docs/reference/releases.mdx |
Clarifies release selection behavior in the install docs page. |
Copilot's findings
- Files reviewed: 6/6 changed files
- Comments generated: 6
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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.
Summary
vX.Y.Z) instead of relying on/releases/latest.Validation
go test ./...go vet ./...cd site && npm ci && npm run buildCloses #296