-
Notifications
You must be signed in to change notification settings - Fork 4k
DNSResolver GA Release 2025-05-01 #27780
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?
DNSResolver GA Release 2025-05-01 #27780
Conversation
Thanks for your contribution! The pull request validation has started. Please revisit this comment for updated status. |
Hi team, when I last made changes in november of 2024, the target branch was to be generation but it does not look like that branch exists anymore? Can I get a confirmation if the correct target is now main? |
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
yes we have the new process for code-gen modules. Please refer to https://eng.ms/docs/cloud-ai-platform/azure-core/azure-experiences-and-ecosystems/azure-portal-and-client-tools-ruhim/azure-cli-tools-azure-cli-powershell-and-terraform/azure-cli-tools/onboarding/azurepowershell/dev_guidance_codegen Please commit all required files such as "generate-info.json" |
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). |
The breaking changes caused by API upgrading
You can do the customization to avoid breaking change https://github.com/Azure/autorest.powershell/blob/main/docs/customization.md For failed test cases, please re-record all test cases. |
Description
The PR adds the new generation of the api-spec version 2025-05-01, the new version introduces three new major changes
Previous PR for generation of 2023-07-01-preview version: #26452
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.md
and reviewed the following information:ChangeLog.md
file(s) appropriatelysrc/{{SERVICE}}/{{SERVICE}}/ChangeLog.md
.## Upcoming Release
header in the past tense.ChangeLog.md
if no new release is required, such as fixing test case only.