openapi-pipeline-app[bot]
commented
1 week ago Next Steps to Merge
Next steps that must be taken to merge this PR:- ❌ This is the public specs repo
mainbranch which is not intended for iterative development.
You must acknowledge that you understand that after this PR is merged, you won't be able to stop your changes from being published to Azure customers.
If this is what you intend, addPublishToCustomerslabel to your PR.
Otherwise, retarget this PR onto a feature branch, i.e. with prefixrelease-(see aka.ms/azsdk/api-versions#release--branches). - ❌ This PR is in purview of the ARM review (label:
ARMReview). This PR must getARMSignedOfflabel from an ARM reviewer.
This PR is not ready for ARM review (label:NotReadyForARMReview). This PR will not be reviewed by ARM until relevant problems are fixed. Consult the rest of thisNext Steps to Mergecomment for details.
Once the blocking problems are addressed, add to the PR a comment with contents/azp run. Automation will re-evaluate this PR and if everything looks good, it will addWaitForARMFeedbacklabel which will put this PR on the ARM review queue.
For details of the ARM review, see aka.ms/azsdk/pr-arm-review - ❌ This PR is
NotReadyForARMReviewbecause it has theVersioningReviewRequiredlabel. - ❌ This PR has at least one change violating Azure versioning policy (label:
VersioningReviewRequired).
To unblock this PR, either a) introduce a new API version with these changes instead of modifying an existing API version, or b) follow the process at aka.ms/brch. - ❌ The required check named
Protected Fileshas failed. Refer to the check in the PR's 'Checks' tab for details on how to fix it and consult the aka.ms/ci-fix guide
PR applying changes from
typespec-nextand bumping to the new versions.Release notes https://azure.github.io/typespec-azure/docs/release-notes/release-2024-11-05/