Refresh azure-mgmt-frontdoor after migrate to Typespec#47639
Conversation
…etwork/FrontDoor/tspconfig.yaml', API Version: 2025-10-01, SDK Release Type: stable, and CommitSHA: '12be16fab6dbfd11c55daefb35c28548f34c3f5c' in SpecRepo: 'https://github.com/Azure/azure-rest-api-specs' Pipeline run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=6475785 Refer to https://eng.ms/docs/products/azure-developer-experience/develop/sdk-release/sdk-release-prerequisites to prepare for SDK release.
There was a problem hiding this comment.
Pull request overview
This PR refreshes the azure-mgmt-frontdoor package after its migration to TypeSpec, regenerating the SDK from spec commit 12be16f (API version 2025-10-01) and promoting it from the 2.0.0b1 beta to a stable 2.0.0 GA release. It fits into the broader effort to migrate management-plane SDKs to TypeSpec-based generation, which restructures models so flattened properties now live under nested properties sub-models.
Changes:
- Promotes the package to a stable
2.0.0release: bumps_version.py, flipsis_stable=trueand theDevelopment Status :: 5 - Production/Stableclassifier, drops Python 3.9 support (now>=3.10), and documents an extensive Features/Breaking-Changes set in the CHANGELOG. - Updates spec/generation metadata (
tsp-location.yaml,_metadata.json,apiview-properties.json) and adds generated API surface snapshots (api.md,api.metadata.yml). - Regenerates client/operation/serialization source from the newer emitter (
0.63.2/ http-client-python^0.33.0), including new duration-numeric serializers and XML fast-path handling in the shared_utilshelpers.
Reviewed changes
Copilot reviewed 16 out of 17 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
azure/mgmt/frontdoor/_version.py |
Version bumped 2.0.0b1 → 2.0.0, matching CHANGELOG. |
CHANGELOG.md |
New 2.0.0 (2026-06-24) entry with Features Added and Breaking Changes. |
pyproject.toml |
Stable flags: is_stable=true, Production/Stable classifier, requires-python>=3.10, +3.14. |
README.md |
Updates tested-Python to 3.10+ and AAD→Microsoft Entra wording. |
tsp-location.yaml / _metadata.json |
Spec commit and emitter/http-client-python version bumps. |
azure/mgmt/frontdoor/_client.py, aio/_client.py |
Self import guard; api_version default-None docstring. Signature credential, subscription_id, base_url verified correct. |
azure/mgmt/frontdoor/_configuration.py, aio/_configuration.py |
Regenerated api_version docstring (default None). |
azure/mgmt/frontdoor/operations/_operations.py, aio/operations/_operations.py |
Regenerated next-link requests now pass headers=_headers (generated). |
azure/mgmt/frontdoor/_utils/serialization.py, _utils/model_base.py |
Regenerated shared helpers: numeric duration formats, header fast-path, XML field plan, default-value handling. |
api.md, api.metadata.yml, apiview-properties.json |
Generated API surface snapshot, hash metadata, and CrossLanguageVersion. |
No issues were found in the reviewable (non-generated) files: version/CHANGELOG/pyproject consistency, stability flags, client signature/name alignment, and README sample code all check out. The remaining changes are extensive regenerated code (including new default-value and XML-deserialization behavior in the shared model base) plus a major GA stable release with many breaking changes, which carries behavioral risk best confirmed by a human.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Live Test Status: Not RunLive tests were not executed for this release:
The 2.0.0 changelog has been optimized (hybrid-model + operation migration notes, container-property grouping, and unused model/enum consolidation) and pushed. |
Configurations: 'specification/frontdoor/resource-manager/Microsoft.Network/FrontDoor/tspconfig.yaml', API Version: 2025-10-01, SDK Release Type: stable, and CommitSHA: '12be16fab6dbfd11c55daefb35c28548f34c3f5c' in SpecRepo: 'https://github.com/Azure/azure-rest-api-specs' Pipeline run: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=6475785 Refer to https://eng.ms/docs/products/azure-developer-experience/develop/sdk-release/sdk-release-prerequisites to prepare for SDK release.