Network Cloud CLI - updating History.rst with missing entry 4.0.0b2#9577
Network Cloud CLI - updating History.rst with missing entry 4.0.0b2#9577necusjz merged 6 commits intoAzure:mainfrom
Conversation
️✔️Azure CLI Extensions Breaking Change Test
|
|
Hi @idanielsteven, |
|
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 adds a missing historical entry for version 4.0.0b2 to the HISTORY.rst file. The entry documents a security fix for a zip/slip vulnerability that was addressed in the beta release between versions 4.0.0b1 and the stable 4.0.0 release.
Changes:
- Added version 4.0.0b2 entry in HISTORY.rst with description of zip/slip vulnerability fix
Release SuggestionsModule: networkcloud
Notes
|
…zure#9577) * initial checking for 2025-07-15 stable CLI * Moving managed network fabric cli to stable version. * updating history file * Network Cloud CLI - updating History.rst with missing entry 4.0.0b2
Network Cloud CLI - updating History.rst with missing entry 4.0.0b2
NOTE: No changes to aaz.
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.