Update azd update success message#7591
Conversation
Agent-Logs-Url: https://github.com/Azure/azure-dev/sessions/6129ef1d-f8cd-498f-89ac-0ff3f84e04b3 Co-authored-by: hemarina <104857065+hemarina@users.noreply.github.com>
azd update success message
There was a problem hiding this comment.
Pull request overview
This PR refines the azd update success output to be shorter and more actionable for users after an update completes.
Changes:
- Updated the success message format string emitted by
azd updateto prompt users to verify withazd --version.
jongio
left a comment
There was a problem hiding this comment.
Two issues with this change:
-
The original "Changes take effect on next invocation" was useful context - it tells users the current process is still the old binary. Dropping it removes info that matters for scripted workflows and user understanding.
-
If "Run
azd --versionto confirm" is desired,ResultMessage.FollowUpis the right place for it - that's where the codebase puts next-step guidance (extension.go:1251, templates.go:475, pipeline.go:262).
The new format also diverges from adjacent messages in this function - line 236 uses "azd is up to date (version %s)" and line 279 uses "Updating azd to %s". Dropping the "azd" subject and switching to "v" prefix creates inconsistency.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Azure Dev CLI Install InstructionsInstall scriptsMacOS/Linux
bash: pwsh: WindowsPowerShell install MSI install Standalone Binary
MSI
Documentationlearn.microsoft.com documentationtitle: Azure Developer CLI reference
|
jongio
left a comment
There was a problem hiding this comment.
Compromise that addresses hemarina's feedback while matching codebase conventions - see inline suggestion.
wbreza
left a comment
There was a problem hiding this comment.
Code Review — PR #7591
Update azd update success message by @copilot
Summary
+1 on @jongio's feedback. The format change drops useful context ("Changes take effect on next invocation"), introduces a style inconsistency with adjacent messages in the same function ("azd is up to date (version %s)" at line 236, "Updating azd to %s" at line 279), and puts next-step guidance in Header instead of FollowUp.
| Priority | Count |
|---|---|
| Medium | 1 |
| Total | 1 |
Overall Assessment: Comment — needs refinement per @jongio's feedback before merge.
Review performed with GitHub Copilot CLI
Co-authored-by: Jon Gallant <2163001+jongio@users.noreply.github.com>
jongio
left a comment
There was a problem hiding this comment.
LGTM. The FollowUp field is the right pattern for next-step guidance, and the wording addresses the product feedback from hemarina. Consistent with adjacent usages in extension.go, templates.go, and env.go.
On a related note I added some ideas in #4948 around improving the update notifications slightly, e.g.
|
Thanks @JeffreyCA. Will follow up the discussion in #4948 |


The success message after
azd updatewas verbose and unclear about next steps. Updated to a shorter, more actionable format.Before:
SUCCESS: Updated azd to version 1.24.0-beta.1-daily.6114472. Changes take effect on next invocation.After:
SUCCESS: Updated to v1.24.0! Run 'azd --version' to confirm.cli/azd/cmd/update.go