adding stack-hci-vm cli 1.15.0 version - #10177
Conversation
|
Hi hvedati, |
|
Azure Pipelines: There may be pipelines that require an authorized user to comment /azp run to run. |
|
/azp run |
|
Azure Pipelines: Successfully started running 2 pipeline(s). |
There was a problem hiding this comment.
🟡 Not ready to approve
It manually edits src/index.json, which the repo PR template states must be updated only by the post-merge automated publish pipeline.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
This review doesn't count toward merge requirements. Sign up for the private preview to control whether Copilot approvals count.
Pull request overview
Updates the published metadata for the stack-hci-vm Azure CLI extension by adding a new 1.15.0 entry to the extension index.
Changes:
- Adds a
stack-hci-vm1.15.0wheel entry (download URL, metadata, sha256) tosrc/index.json.
File summaries
| File | Description |
|---|---|
| src/index.json | Adds a new stack-hci-vm version entry to the extensions index. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 1
- Review effort level: Lite
We're testing this review assessment. Please use 👍 or 👎 to tell us if it's correct.
|
Thank you for your contribution hvedati! We will review the pull request and get back to you soon. |
|
stack-hci-vm |
|
/azp run |
|
Azure Pipelines: Successfully started running 2 pipeline(s). |
🤖 PR Validation — ️✔️ All clear
This checklist is used to make sure that common guidelines for a pull request are followed.
Related command
General Guidelines
azdev style <YOUR_EXT>locally? (pip install azdevrequired)python scripts/ci/test_index.py -qlocally? (pip install azdevrequired)For new extensions:
About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update
src/index.jsonautomatically.You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify
src/index.json.