[Confcom] Fix Azure/azure-cli-extensions#10014: az confcom acipolicygen: Fix NumPy 2.0 compatibility

[Copilot]

az confcom acipolicygen fails on systems with NumPy 2.0 (e.g., Fedora 42, Python 3.13) because deepdiff==6.3.0 (bundled in confcom ≤1.3.0) references np.float_, which was removed in NumPy 2.0.

Changes

• setup.py: Bump version 2.1.0 → 2.1.1. The deepdiff~=8.6.1 constraint was already present (introduced in 1.3.1) and resolves to a NumPy 2.0-compatible build (np.double replaces the removed np.float_). Version bump ensures users with stale installs are prompted to upgrade.
• HISTORY.rst: Add 2.1.1 release entry documenting the NumPy 2.0 fix.

---

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

Related command

az confcom acipolicygen

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? (azdev required; see .azure-pipelines/templates/azdev_setup.yml for the install command until azdev==0.2.11b1 is on PyPI)
• 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]

️✔️Azure CLI Extensions Breaking Change Test

️✔️Non Breaking Changes

[azure-client-tools-bot-prd]

Hi @copilot,
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]

Confcom