-
Notifications
You must be signed in to change notification settings - Fork 4.1k
AFD Upgrade version to 0601 #28254
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
AFD Upgrade version to 0601 #28254
Conversation
| Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR upgrades the API version for Azure CDN operations from "2025-04-15" to "2025-06-01" across test recording files. This is a version update to align with the newer API version that includes potentially improved features or bug fixes.
- Update API version from 2025-04-15 to 2025-06-01 in CDN test recordings
- Update resource group references from testps-rg-fz5y to testps-rg-hbtl
- Update test execution timestamps and associated metadata
Reviewed Changes
Copilot reviewed 125 out of 255 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| src/Cdn/Cdn.Autorest/test/New-AzFrontDoorCdnCustomDomain.Recording.json | Updates API version and test recording data for FrontDoor CDN custom domain operations |
| src/Cdn/Cdn.Autorest/test/New-AzCdnProfile.Recording.json | Updates API version and test recording data for CDN profile creation operations |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
Hi @Ptnan7, the ChangeLog file path is src/Cdn/Cdn/ChangeLog.md. Please add a line right below Upcoming Release using the past tense to describe the purpose of this PR. Thanks. |
|
This PR was labeled "needs-revision" because it has unresolved review comments or CI failures. |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
@Ptnan7 please help check whether the breaking change reported is as expected. If there are really breaking changes, this PR is needed to be held until next major release |
|
Closing the PR for lack of activity. Feel free to reopen to continue working on it. Thanks 😀 |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are breaking changes detected that have not been preannounced. Either target the next breaking change window May 2026, or make sure the PR contains no breaking change.
Check the log of the static analysis pipeline for details.
| @@ -20,6 +20,9 @@ | |||
|
|
|||
| ## Upcoming Release | |||
|
|
|||
| ## Version 5.1.0 | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please remove this line of version, make sure new entries go directly below line 21. This is because the next version will be calculated automatically during release process.
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
|
To the author of the pull request, |
Description
Mandatory Checklist
Please choose the target release of Azure PowerShell. (⚠️ Target release is a different concept from API readiness. Please click below links for details.)
Check this box to confirm: I have read the Submitting Changes section of
CONTRIBUTING.mdand reviewed the following information:ChangeLog.mdfile(s) appropriatelysrc/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.## Upcoming Releaseheader in the past tense.ChangeLog.mdif no new release is required, such as fixing test case only.