Conversation
|
Validation for Breaking Change Starting...
Thanks for your contribution! |
|
Hi @najian, |
|
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 updates the HISTORY.rst file for the containerapp extension by revising the release notes.
- Updated the command entry for "az containerapp sessionpool update" in the upcoming release section.
- Removed the duplicate entry for "az containerapp sessionpool update" from version 1.1.0b5 to avoid confusion.
Comments suppressed due to low confidence (1)
src/containerapp/HISTORY.rst:14
- It appears that the 'az containerapp sessionpool update' command is documented twice in different sections. Confirm that the duplicate entry removal is intentional to maintain clear and concise release notes.
-* 'az containerapp sessionpool update': Support `--mi-system-assigned`, `--mi-user-assigned` and `--registry-identity`
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 @najian Release SuggestionsModule: containerapp
Notes
|
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.