(DO NOT MERGE) Updating capabilities in a non-simple way.#9160
(DO NOT MERGE) Updating capabilities in a non-simple way.#9160richardpark-msft wants to merge 1 commit into
Conversation
|
Azure Pipelines: 22 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
|
Perfect, failure was expected since I did a non-simple change: https://github.com/Azure/azure-dev/actions/runs/29450244109/job/87470654819?pr=9160 |
|
Second one worked, since I made it a simple update: https://github.com/Azure/azure-dev/actions/runs/29450328687/job/87470930514?pr=9160 |
cfd204b to
3dda3df
Compare
|
And the last type - a non-registry related change runs the workflow but it exits immediately: https://github.com/Azure/azure-dev/actions/runs/29450416355/job/87471216394?pr=9160 |
jongio
left a comment
There was a problem hiding this comment.
This is a CI trigger experiment - the only change is an empty cli/azd/dummy.txt, so there's no code or workflow logic to review on the diff itself. Flagging just one thing for cleanup: since this is marked DO NOT MERGE, make sure the branch is closed or the dummy file is dropped before any real change lands on it, so the empty file doesn't leak into the tree.
3dda3df to
a397aa4
Compare
cfd204b to
3dda3df
Compare
3dda3df to
a397aa4
Compare
jongio
left a comment
There was a problem hiding this comment.
One thing on this new 0.8.0 entry beyond the duplicate capability list already flagged: the artifacts point at the old release, so it would ship the wrong binaries. Details inline.
| "usage": "azd demo copilot [--model <model>] [--resume]" | ||
| } | ||
| ], | ||
| "artifacts": { |
There was a problem hiding this comment.
All of these 0.8.0 artifact URLs point at the azd-ext-microsoft-azd-demo_0.7.0 release, so installing 0.8.0 would download the 0.7.0 binaries. Together with the capability list being identical to 0.7.0, this 0.8.0 entry is a copy of 0.7.0 with only the version bumped. For a real capability update, the artifact URLs and checksums need to point at an actual 0.8.0 release.
There was a problem hiding this comment.
You are correct. But what does your meta-awareness tell you about this PR?
There was a problem hiding this comment.
Meta-awareness: this reads as a deliberate probe of how automated review reacts to PR interactions rather than a real change. The azd-check-pr-interactions branch name and the DO NOT MERGE title give it away, and HEAD has since been force-pushed back to just an empty cli/azd/dummy.txt. So the registry.json issue I flagged is gone from the current diff and there is nothing left to review on this commit.
If the 0.8.0 registry entry comes back, the two things that make it real: the artifact URLs still point at the azd-ext-microsoft-azd-demo_0.7.0 release, and the capability list is a duplicate of 0.7.0. Fix those before it lands.
cfd204b to
3dda3df
Compare
Azure Dev CLI Install InstructionsInstall scriptsMacOS/Linux
bash: pwsh: WindowsPowerShell install MSI install Standalone Binary
MSI
Documentationlearn.microsoft.com documentationtitle: Azure Developer CLI reference
|
No description provided.