Conversation
️✔️Azure CLI Extensions Breaking Change Test
|
|
Hi @gaurimadhok, |
|
Thank you for your contribution! We will review the pull request and get back to you soon. |
|
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). pip install azdev --upgrade
azdev setup -c <your azure-cli repo path> -r <your azure-cli-extensions repo path>
|
There was a problem hiding this comment.
Pull Request Overview
This PR bumps the package version in setup.py to prepare for the next beta release.
- Updated the
VERSIONconstant from1.0.0b1to1.0.0b2. - (Reminder) Per guidelines, the changelog in HISTORY.rst should be updated alongside this bump.
CodeGen Tools Feedback CollectionThank 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 @gaurimadhok Release SuggestionsModule: providerhub
Notes
|
|
[Release] Update index.json for extension [ providerhub-1.0.0b2 ] : https://dev.azure.com/msazure/One/_build/results?buildId=126455208&view=results |
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 azdevrequired)python scripts/ci/test_index.py -qlocally? (pip install wheel==0.30.0required)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.jsonautomatically.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.