[Containerapp] Release version 1.2.0b5#9402
Conversation
️✔️Azure CLI Extensions Breaking Change Test
|
|
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>
|
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 |
|
There was a problem hiding this comment.
Pull Request Overview
This PR bumps the version of the containerapp extension from 1.2.0b4 to 1.2.0b5 and documents the changes in the release history.
- Version updated in setup.py from 1.2.0b4 to 1.2.0b5
- New version section added to HISTORY.rst with release notes
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| src/containerapp/setup.py | Updated VERSION constant from '1.2.0b4' to '1.2.0b5' |
| src/containerapp/HISTORY.rst | Added new 1.2.0b5 section with release notes |
| upcoming | ||
| ++++++ | ||
|
|
||
| 1.2.0b5 | ||
| ++++++ |
There was a problem hiding this comment.
The 'upcoming' section should appear after the current release section (1.2.0b5), not before it. The 'upcoming' section is meant to collect changes for the next version, so it should be positioned above the most recent release but the release notes for 1.2.0b5 should be under the 1.2.0b5 heading. Consider restructuring so that 1.2.0b5 appears first with its changes, followed by an empty 'upcoming' section below it for future changes.
|
[Release] Update index.json for extension [ containerapp ] : https://dev.azure.com/msazure/One/_build/results?buildId=142986689&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.