Closed Pan-Qi closed 1 week ago
Hi @Pan-Qi, 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.
Thank you for your contribution! We will review the pull request and get back to you soon.
Thank you for using our CodeGen tool. We value your feedback, and we would like to know how we can improve our product. Please take a few minutes to fill our codegen survey
Hi @Pan-Qi
Release Suggestions
Module: azure-firewall
- Please log updates into to
src/azure-firewall/HISTORY.rst
- Update
VERSION
to1.2.2
insrc/azure-firewall/setup.py
Notes
- For more info about extension versioning, please refer to Extension version schema
we need to update them to trigger a release
[Release] Update index.json for extension [ azure-firewall ] : https://dev.azure.com/azclitools/release/_build/results?buildId=207083&view=results
resolve: https://github.com/Azure/azure-cli/issues/29854 [Network] Add support for Azure Firewall Byopip feature
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
.