{AKS} Vendor new SDK and bump API version to 2026-03-01#33384
{AKS} Vendor new SDK and bump API version to 2026-03-01#33384FumingZhang wants to merge 1 commit into
Conversation
- Update SDK version in setup.py and requirements files - Replace api-version=2026-02-01 with 2026-03-01 in 229 test recordings
️✔️AzureCLI-FullTest
|
️✔️AzureCLI-BreakingChangeTest
|
|
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 azure-mgmt-containerservice SDK dependency from 41.1.0 to 41.2.0 and refreshes AKS test VCR recordings to use the new 2026-03-01 Container Service REST API version (replacing 2026-02-01).
Changes:
- Bump
azure-mgmt-containerserviceto~=41.2.0insetup.pyand pin to==41.2.0in all three OS-specificrequirements.py3.*.txtfiles. - Rewrite
api-version=2026-02-01→api-version=2026-03-01across the AKS test recording YAML fixtures.
Reviewed changes
Copilot reviewed 142 out of 233 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
src/azure-cli/setup.py |
Bump azure-mgmt-containerservice constraint to ~=41.2.0. |
src/azure-cli/requirements.py3.{windows,Linux,Darwin}.txt |
Pin azure-mgmt-containerservice to ==41.2.0 on each OS. |
src/azure-cli/azure/cli/command_modules/acs/tests/latest/recordings/*.yaml (many) |
Update recorded request URIs from api-version=2026-02-01 to api-version=2026-03-01 to match the new SDK. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Related command
Description
{AKS} Vendor new SDK and bump API version to 2026-03-01
Testing Guide
History Notes
[Component Name 1] BREAKING CHANGE:
az command a: Make some customer-facing breaking change[Component Name 2]
az command b: Add some customer-facing featureThis checklist is used to make sure that common guidelines for a pull request are followed.
The PR title and description has followed the guideline in Submitting Pull Requests.
I adhere to the Command Guidelines.
I adhere to the Error Handling Guidelines.