Closed blackchoey closed 1 day ago
Hi @blackchoey, 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.
VERSION
to be 2.0.0
in src/apic-extension/setup.py
stable
/preview
label to modify it.major
/minor
/patch
/pre
label to adjust it.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
/azp run
i saw there are a lot of "breaking changes" in https://github.com/Azure/azure-cli-extensions/pull/7677#issuecomment-2144543999, are they all expected?
i saw there are a lot of "breaking changes" in #7677 (comment), are they all expected?
@necusjz Yes, they're expected. We want to leverage the last chance to make some breaking changes to ensure the CLI is in the best shape. There're 3 kind of breaking changes:
-n
instead -s
to ask for resource name./azp run
/azp run
/azp run
[Release] Update index.json for extension [ apic-extension ] : https://dev.azure.com/azclitools/release/_build/results?buildId=169884&view=results
This PR include changes for apic-extension GA
Related command
az apic *
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
.