Skip to content

2025-06-01 api version #34214

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

Open
wants to merge 10 commits into
base: main
Choose a base branch
from

Conversation

andrewjhopkins
Copy link
Member

Choose a PR Template

Switch to "Preview" on this description then select one of the choices below.

Click here to open a PR for a Data Plane API.

Click here to open a PR for a Control Plane (ARM) API.

Click here to open a PR for only SDK configuration.

@andrewjhopkins andrewjhopkins requested a review from a team as a code owner April 24, 2025 16:29
Copy link

openapi-pipeline-app bot commented Apr 24, 2025

Next Steps to Merge

Next steps that must be taken to merge this PR:
  • ❌ This PR targets either the main branch of the public specs repo or the RPSaaSMaster branch of the private specs repo. These branches are not intended for iterative development. Therefore, you must acknowledge you understand that after this PR is merged, the APIs are considered shipped to Azure customers. Any further attempts at in-place modifications to the APIs will be subject to Azure's versioning and breaking change policies. Additionally, for control plane APIs, you must acknowledge that you are following all the best practices documented by ARM at aka.ms/armapibestpractices. If you do intend to release the APIs to your customers by merging this PR, add the PublishToCustomers label to your PR in acknowledgement of the above. Otherwise, retarget this PR onto a feature branch, i.e. with prefix release- (see aka.ms/azsdk/api-versions#release--branches).
  • ❌ The required check named Automated merging requirements met has failed. This is the final check that must pass. 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. In addition, refer to step 4 in the PR workflow diagram

Copy link

openapi-pipeline-app bot commented Apr 24, 2025

PR validation pipeline restarted successfully. If there is ApiView generated, it will be updated in this comment.

@github-actions github-actions bot added the brownfield Brownfield services will soon be required to convert to TypeSpec. See https://aka.ms/azsdk/typespec. label Apr 24, 2025
Copy link

github-actions bot commented Apr 24, 2025

API Change Check

APIView identified API level changes in this PR and created the following API reviews

Language API Review for Package
Swagger CallAutomation-PhoneNumbers

@andrewjhopkins andrewjhopkins added the offline-review-requested Service team has requested PR review be conducted offline. label May 12, 2025
@weidongxu-microsoft
Copy link
Member

weidongxu-microsoft commented May 19, 2025

API Version Update:

Updated from version 2025-04-01 to 2025-06-01

1. Added "mobile" Phone Number Type:

2. Added "mobile" as a new enum value alongside the existing "geographic" and "tollFree" types
- This addition appears consistently in all places where phone number types are defined
- Updated all corresponding descriptions to include "Mobile" in the text (e.g., changing "e.g. Geographic, TollFree" to "e.g. Geographic, TollFree, Mobile")

3. Added New Query Parameter:
- Added a new "phoneNumberType" query parameter to filter phone numbers by type (geographic, tollFree, or mobile)
6c6
<     "version": "2025-04-01"
---
>     "version": "2025-06-01"
30c30
<             "description": "Filter by numberType, e.g. Geographic, TollFree.",
---
>             "description": "Filter by numberType, e.g. Geographic, TollFree, Mobile.",
35c35,36
<               "tollFree"
---
>               "tollFree",
>               "mobile"
280a282,296
>           },
>           {
>             "in": "query",
>             "name": "phoneNumberType",
>             "description": "Filter by numberType, e.g. Geographic, TollFree, Mobile.",
>             "type": "string",
>             "enum": [
>               "geographic",
>               "tollFree",
>               "mobile"
>             ],
>             "x-ms-enum": {
>               "name": "PhoneNumberType",
>               "modelAsString": true
>             }
345c361
<             "description": "Filter by numberType, e.g. Geographic, TollFree.",
---
>             "description": "Filter by numberType, e.g. Geographic, TollFree, Mobile.",
349c365,366
<               "tollFree"
---
>               "tollFree",
>               "mobile"
1534c1551,1552
<             "tollFree"
---
>             "tollFree",
>             "mobile"
1648c1666
<           "description": "The type of phone numbers to search for, e.g. geographic, or tollFree.",
---
>           "description": "The type of phone numbers to search for, e.g. geographic, tollFree, mobile.",
1651c1669,1670
<             "tollFree"
---
>             "tollFree",
>             "mobile"
1713c1732
<           "description": "The phone number's type, e.g. geographic, or tollFree.",
---
>           "description": "The phone number's type, e.g. geographic, tollFree, mobile.",
1716c1735,1736
<             "tollFree"
---
>             "tollFree",
>             "mobile"
1812c1832
<           "description": "The phone number's type, e.g. geographic, tollFree.",
---
>           "description": "The phone number's type, e.g. geographic, tollFree, mobile.",
1815c1835,1836
<             "tollFree"
---
>             "tollFree",
>             "mobile"
1879c1900,1901
<             "tollFree"
---
>             "tollFree",
>             "mobile"
1996c2018,2019
<             "tollFree"
---
>             "tollFree",
>             "mobile"

@mikekistler mikekistler linked an issue May 19, 2025 that may be closed by this pull request
Copy link
Member

@mikekistler mikekistler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. 👍

@mikekistler mikekistler added the APIStewardshipBoard-SignedOff The Azure API Stewardship team has reviewed and approved the changes. label May 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
APIStewardshipBoard-SignedOff The Azure API Stewardship team has reviewed and approved the changes. brownfield Brownfield services will soon be required to convert to TypeSpec. See https://aka.ms/azsdk/typespec. data-plane new-api-version offline-review-requested Service team has requested PR review be conducted offline.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[IC3 ACS Management GW ] REST API Review
4 participants