[DNM] Adding new version 1.12.3 to revert to last known good version (1.11.9)

[han-sogawa-microsoft]

---

This checklist is used to make sure that common guidelines for a pull request are followed.

Related command

General Guidelines

• Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
• Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)
• My extension version conforms to the Extension version schema

For new extensions:

• My extension description/summary conforms to the Extension Summary Guidelines.

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.json automatically.
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.

[azure-client-tools-bot-prd]

Validation for Breaking Change Starting...

Thanks for your contribution!

[azure-client-tools-bot-prd]

Hi @han-sogawa-microsoft,
Please write the description of changes which can be perceived by customers into HISTORY.rst.
If you want to release a new extension version, please update the version in setup.py as well.

[yonzhan]

Thank you for your contribution! We will review the pull request and get back to you soon.

[github-actions]

The git hooks are available for azure-cli and azure-cli-extensions repos. They could help you run required checks before creating the PR.

Please sync the latest code with latest dev branch (for azure-cli) or main branch (for azure-cli-extensions).
After that please run the following commands to enable git hooks:

pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>

[github-actions]

• For more info about extension versioning, please refer to Extension version schema

[Copilot]

Pull request overview

Adds an entry to the extension index intended to introduce stack-hci-vm version 1.12.3 as a rollback to the last known good 1.11.9.

Changes:

• Updates src/index.json to include a new stack-hci-vm entry labeled 1.12.3
• Points the new entry at the existing 1.11.9 wheel artifact (URL/filename/digest)

[Copilot]

The added entry claims version 1.12.3, but its downloadUrl/filename and sha256Digest point to the existing 1.11.9 wheel (and 1.11.9 already appears earlier in this list). This creates inconsistent metadata and will likely cause clients to install/report the wrong extension version. Publish/reference a real 1.12.3 wheel (URL/filename/digest) or keep the version as 1.11.9 and avoid duplicating the existing entry.

[Copilot]

This PR edits src/index.json directly, but the PR description/template explicitly says index.json is updated automatically after merge and should not be modified in the PR. If that process still applies, revert this index.json change and instead update the extension's setup.py/HISTORY.rst; the publishing pipeline will generate the index update.