forked from Azure/azure-rest-api-specs
-
Notifications
You must be signed in to change notification settings - Fork 9
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
DNR brInfo_cross_ver_brch
branch
#3411
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Next Steps to MergeNext steps that must be taken to merge this PR:
|
Swagger Generation Artifacts
|
Generated ApiView
|
This was referenced Jul 16, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
DO NOT REVIEW! This is a test PR created by kojamroz from branch
brInfo_cross_ver_brch
.Information about this PR extracted from
BRANCH_INFO.md
This branch was created by kojamroz on 6/26/2024
This branch is expected to trigger cross-version breaking change report between stable version.
In addition, the TypeSpec requirement check should not trigger.
It differs from main as follows:
1. It introduces a new directory:
specification/alertsmanagement/resource-manager/Microsoft.AlertsManagement/stable/2024-05-01
which is a copy of:
specification/alertsmanagement/resource-manager/Microsoft.AlertsManagement/stable/2023-03-01
2. In the new directory the following file:
specification/alertsmanagement/resource-manager/Microsoft.AlertsManagement/stable/2024-05-01/PrometheusRuleGroups.json
Differs from its original. Its
operationId
has been changed. It is now:"operationId": "CROSS_VER_BREAKING_CHANGE_TEST_PrometheusRuleGroups_ListBySubscription",
instead of the original:
"operationId": "PrometheusRuleGroups_ListBySubscription",
In addition, all files in the newly introduced directory got their
"version"
updated to be"2024-05-01"
.3. The README:
specification/alertsmanagement/resource-manager/readme.md
The default tag has been changed to
package-2024-05
and following entry was added: