Closed wangzelin007 closed 1 week ago
Hi @wangzelin007, 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.
CI
Latest setuptools adds a vendored wheel 0.4.3 to generate wheel and it does not generate metadata.json. Related PR: https://github.com/pypa/setuptools/pull/4369
Setuptools 70.1.0 was released on Jun 19. The latest setuptools adds a vendored wheel 0.4.3 to generate wheel and it does not generate metadata.json. Related PR: Adopted the bdist_wheel command from "wheel" by agronholm · Pull Request #4369 · pypa/setuptools (github.com) Installing setuptools with a version higher than 70.0.0 will not generate metadata.json. Pin setuptools version to 70.0.0 to unblock extension release.![image](https://github.com/Azure/azure-cli-extensions/assets/18628534/4f449eb4-f0da-45f5-87c5-cfc688b79b30)
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 azdev
required)python scripts/ci/test_index.py -q
locally? (pip install wheel==0.30.0
required)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.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
.