refresh from main#43551
Closed
baywet wants to merge 32 commits into
Closed
Conversation
Signed-off-by: Vincent Biret <vibiret@microsoft.com>
…ain-merge Signed-off-by: Vincent Biret <vibiret@microsoft.com>
…es for Java (#43358) * Add Java client name overrides for VoiceLive types and properties * Add JS client name overrides for VoiceLive duration/offset properties * Rename Java token usage accessors to counts * Pin Java SDK generation to GA API version * format --------- Co-authored-by: Yulin Li <liyulin@pku.edu.cn>
* Pin VoiceLive C#, HTTP C#, and Java emitters to 2026-04-10 * name changes * Update tspconfig.yaml * test removal of child id * update schemas * add customization to sdk --------- Co-authored-by: Emily Jiji <emilyjiji@microsoft.com>
* update config * update config * update config * Fix emitter-output-dir formatting in tspconfig.yaml * Update tspconfig.yaml * Fix formatting in tspconfig.yaml * update
* Update client.tsp * Update client.tsp
…ain-merge Signed-off-by: Vincent Biret <vibiret@microsoft.com>
* Change namespace casing and location in examples * Update namespace casing for HorizonDb examples * Revert location * Remove sourceClusterResourceId from Clusters_CreateOrUpdate example * Update fully qualified domain names in HorizonDB examples * Update zonePlacementPolicy to BestEffort in HorizonDB examples * Fix resource provider naming inconsistencies in HorizonDb examples - Updated resource provider names from "Microsoft.HorizonDB" to "Microsoft.HorizonDb" in various example JSON files for consistency. - Modified resource IDs in examples for Clusters, FirewallRules, ParameterGroups, Pools, PrivateEndpointConnections, and Replicas to reflect the correct casing. - Ensured that all example responses and requests align with the updated naming conventions. * Fix casing inconsistencies for HorizonDB in API documentation and models * Fix resource type casing in HorizonDb examples to use consistent casing for Microsoft.HorizonDb
* Add CognitiveServices stable API version 2026-03-01 - Add v2026_03_01 to version enum in main.tsp - Copy TypeSpec examples from 2026-01-15-preview, update api-version - Compile TypeSpec to generate cognitiveservices.json (88 paths, 290 defs) - Generated RM examples (160 files, all referenced, zero orphans) - Update readme.md: default tag to package-2026-03-01, add tag section - Single-track versioning: all preview features promoted to stable - New vs prev stable: +1 path (ComputeOperations), +6 definitions * Gate preview-only features from 2026-03-01 stable with @removed decorators Add @removed(Versions.v2026_03_01) to 13 features first introduced in 2026-01-15-preview that should remain preview-only: ComputeOperation.tsp (4): ComputeOperationStatus model, ComputeOperations interface, ComputeOperationStatusProperties model, ComputeOperationStatusType union ManagedNetworkSettingsPropertiesBasicResource.tsp (1): delete operation models.tsp (8): QuotaScopeType union, foundryAutoUpgrade property, FoundryAutoUpgradeMode union, FoundryAutoUpgrade model, scopeType/scopeId on Usage, scopeId/scopeType on ModelSkuCapacityProperties Cascading changes: - Remove 14 TypeSpec examples (2 removed ops + 12 scope-variants) - Remove 14 RM examples (matching orphaned references) - Clean scopeType/scopeId from 4 base examples - Remove NestedResourcesMustHaveListOperation suppression - Recompile: 87 paths, 284 defs (down from 88/290) * Add CognitiveServices preview API version 2026-03-15-preview swagger Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Recompile 2026-03-15-preview swagger after customTopics removal Merge main to pick up @removed(Versions.v2025_10_01_preview) decorators for customTopics, CustomTopicConfig, and RaiTopicConfig from PR #42012. Recompile to remove these definitions from 2026-03-15-preview output. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * add accelerator usages API details * add changes as per PR * accelerator usage api changes * add accelerator change * add format for subs id * Revert AcceleratorUsages API changes from PR #42466 (#42469) Reverts commits 9bd196e..0cca7e2 which added AcceleratorUsages operation and models directly to swagger JSON. These changes need to be re-added properly via TypeSpec source files. * Users/chunyli/cogsvc managed compute deployment (#42130) * Add ManagedCompute deployment API * mark model as non-required * fix gated error * fix unknown word * Add example * check in generated examples * update spec * fix lint * resolve comments * resolve comments * resolve comments * resolve comments * fix lint * fix lint * fix format * resolve comments * switch from AcceleratorDeployment to ManagedComputeDeployment * update suppresion * resolve comments * Add CognitiveServices stable API version 2026-05-01 TypeSpec enum, compiled cognitiveservices.json, examples, readme.md tag section. Feature gating: 13 existing @removed/@added pairs extended to triplets, 7 new @removed(v2026_05_01) for ManagedComputeDeployment + PatchResourceSku (kept preview-only per user decision). 7 orphaned examples cleaned. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Regenerate stable/2026-05-01 with TSP 1.12 + Phase 3 QuotaScopeType cleanup Phase 2: Regenerated cognitiveservices.json from merged TypeSpec source using @typespec/compiler 1.12.0. Picks up changes from interim PRs: - VmManagedCompute deployment shape (#43238) — computeId, priority, deploymentTemplate type - New compute surface: Compute, ManagedComputeCapacity, ContainerInstance, ComputeProvisioningState (#42324, #42642, #42794) - Model-Router enum correction accuracy->quality (#42375) - x-ms-pageable on batchOutboundRules POST (#42435) - RaiExternalSafetyProvider 201 response fix (#42414) - DELETE managedNetworks promotion to stable (#42585) — restores GA operation that was incorrectly gated out of stable/2026-05-01 by the swagger-agent's lone-@removed fallback bug Regression audit vs previous stable (2026-03-01): 0 operation regressions, 0 definition regressions, 0 property regressions, 0 enum value regressions. 19 new operations and 29 new definitions added — all need GA feature-confirmation with owners in a follow-up step. Phase 3: QuotaScopeType example cleanup. The TSP recompile already deleted the 12 orphan scope-variant files automatically. Stripped remaining scopeType/scopeId properties from the 4 base example response bodies in both TSP source and RM output: - GetUsages.json, ListUsages.json - ListModelCapacities.json, ListLocationBasedModelCapacities.json This resolves the 26 OBJECT_ADDITIONAL_PROPERTIES Swagger ModelValidation errors. Verification: - All 138 RM example files referenced by x-ms-examples (0 orphans) - All 138 TSP source examples referenced by x-ms-examples (0 orphans) - Zero scopeType/scopeId occurrences in any base example file Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Phase 3 fix: delete 12 QuotaScopeType scope-variant example files Previous Phase 3 attempt only stripped scopeType/scopeId from base example response bodies but left the 12 scope-variant example files in the TSP source examples/2026-05-01/ directory. The TypeSpec compiler auto-discovers any .json file in the version examples directory by its operationId field and emits x-ms-examples references, causing the files to be copied to RM output and validated against the schema. Since QuotaScopeType is gated out of stable/2026-05-01, the response bodies in these examples contain properties not allowed by the schema, causing 26 OBJECT_ADDITIONAL_PROPERTIES Swagger ModelValidation errors. Deleted from TSP source (compiler-managed copy to RM output handled by clean rebuild): - GetUsages{Classic,DataZone,Global}Scope.json - ListUsages{Classic,DataZone,Global}Scope.json - ListModelCapacities{Classic,DataZone,Global}Scope.json - ListLocationBasedModelCapacities{Classic,DataZone,Global}Scope.json After clean rebuild of stable/2026-05-01 RM directory: zero scope- variant references in compiled swagger, zero scopeType/scopeId in remaining base examples. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Sync new stable suppressions block with previous preview The swagger-agent skill (sub-skill-swagger.md Step 7) directs new tag sections to copy the previous tag of the same TRACK (stable->stable, preview->preview). For CognitiveServices this is inconsistent with its own content-flow rule: CogSvc is single-track, so new stable inherits content from previous preview. The result was that new stable 2026-05-01 inherited preview content (Compute, Workbench, ManagedCompute*, EvaluateDeploymentPolicies, additional PATCH/DELETE paths) but only the previous-stable suppression block (17 entries), dropping 4 net new codes and several path extensions added in preview. This commit replaces the new stable's suppressions block with the previous preview's block (21 entries). Manual diff confirmed the preview block is a strict superset in path coverage with no entries unique to the previous stable — every 'stable-only' entry has a matching preview entry with broader 'where:' lists or more detailed 'reason:' text. Net effect: - +NestedResourcesMustHaveListOperation (ComputeOperationStatus) - +RequiredPropertiesMissingInResourceModel (ManagedComputeUsageListResult) - +AvoidAdditionalProperties (EvaluateDeploymentPoliciesResponse.results) - +PatchBodyParametersSchema for Workbench - PatchBodyParametersSchema 'where' extended (+4 paths: managedComputeDeployments, computes, computes.computeType, computes.schema) - DeleteResponseCodes 'where' extended (+managedComputeDeployments) - More-detailed reasons on ProvisioningStateSpecifiedForLROPut and 2x AvoidAdditionalProperties Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Add missing example files for ops inherited from preview via merge After the main merge brought new operations into the new stable (Computes_*, Workbenches_*, ManagedComputeUsagesOperationGroup_List, ManagedComputeCapacities_List, Accounts_EvaluateDeploymentPolicies, plus restored ManagedNetworkSettings_Delete and Projects_Delete from prior commit), 20 operations had no x-ms-examples in the compiled stable swagger, triggering 22 XMS_EXAMPLE_NOTFOUND_ERROR violations in Swagger ModelValidation. The TypeSpec compiler auto-discovers example files in the version's examples/<version>/ directory by matching the file's operationId field. Example files for these operations existed in examples/2026-03-15-preview/ but not in examples/2026-05-01/. Copied 22 example files from the preview version directory to the new stable version directory and updated their api-version field from 2026-03-15-preview to 2026-05-01: ListManagedComputeUsages, ListManagedComputeCapacities, ListComputes, GetCompute, GetContainerInstanceCompute, PutCompute, PutContainerInstanceCompute, UpdateCompute, DeleteCompute, RestartContainerInstanceCompute, StartContainerInstanceCompute, StopContainerInstanceCompute, EvaluateDeploymentPolicies, ListWorkbenches, GetWorkbench, PutWorkbench, UpdateWorkbench, DeleteWorkbench, RestartWorkbench, StartWorkbench, StopWorkbench, ManagedNetwork/deleteManagedNetworkV2 After clean rebuild: 0 operations missing examples in compiled swagger. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Gate preview-only features out of 2026-05-01 stable Per direction: features first introduced in 2026-03-15-preview should not graduate to stable in this cycle. The new stable 2026-05-01 should be content-identical to the previous stable 2026-03-01 (since the original PR (2026-04-21) had no new GA-approved additions beyond 2026-03-01, and all subsequent additions to preview during the 38-day PR lifespan are preview-only). Added @removed(Versions.v2026_05_01) decorators to 32 elements: models.tsp (26 entries): ClusterComputeProperties, ComputeListResult, ComputeProperties, ComputeProvisioningState, ComputeType, ConnectivityEndpoints, ContainerInstanceComputeProperties, DeploymentPolicyEvaluationResult, DeploymentSizeCapacity, EvaluateDeploymentPoliciesDeployment, EvaluateDeploymentPoliciesDeploymentProperties, EvaluateDeploymentPoliciesRequest, EvaluateDeploymentPoliciesResponse, ManagedComputeCapacityListResult, ManagedComputeCapacityProperties, ManagedComputeDeploymentInfo, ManagedComputeUsage, ManagedComputeUsageListResult, PolicyAssignmentEvaluationDetails, PolicyEvaluationOutcome, PolicyExpressionEvaluationDetails, Pool, SshSettings, VmPriority, WorkbenchListResult, WorkbenchProperties Compute.tsp: Compute model + Computes interface Workbench.tsp: Workbench model + Workbenches interface ManagedComputeCapacity.tsp: ManagedComputeCapacity model + ManagedComputeCapacities interface ManagedComputeUsages.tsp: ManagedComputeUsagesOperationGroup interface Account.tsp: evaluateDeploymentPolicies operation All decorators placed immediately after the existing @added(Versions.v2026_03_15_preview) per agent decorator-ordering rule. After clean rebuild: 2026-03-01 stable: 87 paths, 280 defs, 145 ops 2026-05-01 stable: 87 paths, 280 defs, 145 ops Delta ops/defs/paths: 0/0/0 — content-identical to 2026-03-01 Cleanup: - Deleted 21 example files for now-gated operations (Compute, Workbench, ManagedComputeCapacities, ManagedComputeUsages, EvaluateDeploymentPolicies) from both TSP source and RM output. Final example count: 127 = 127 refs. - Reverted readme.md package-2026-05-01 suppressions to the 17-entry set from package-2026-03-01 (the 21-entry preview set is no longer needed because the content those entries suppressed is gated out). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Add missing 200 response to Projects_Delete example The Projects_Delete operation defines response codes 200, 202, 204, and default in the swagger spec, but the DeleteProject.json example only included 202 and 204. This caused Swagger ModelValidation error RESPONSE_STATUS_CODE_NOT_IN_EXAMPLE for the 200 response code. The previous stable 2026-03-01's DeleteProject.json example does include 200 as an empty body response. Restored the 200 entry to match the 2026-03-01 example structure. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: abpatelmicrosoft <abpatel@microsoft.com> Co-authored-by: Chunyu Li <79233053+ChunyuMSFT@users.noreply.github.com> Co-authored-by: Swagger Agent <swagger-agent@noreply.github.com>
…5-01-preview API version (#43673) Adds transparentDataEncryptions resource type, capabilities on TaskHubs, and managed identity support on Schedulers (plus a restart action). Existing API versions and model names are preserved as-is. Co-authored-by: Bernd Verst <beverst@microsoft.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* datalake-go * go datalake * expiresOn * expires on * datalake updates * format * suppressions for batch SDK building * fix suppressions * add missing sub-rules --------- Co-authored-by: Joel Hendrix <jhendrix@microsoft.com>
Co-authored-by: Vikeshi Tiwari <vikestiwari@microsoft.com> Co-authored-by: Tejaswi Salaigari <tsalaigari@microsoft.com>
Co-authored-by: Chidozie Ononiwu <chononiw@microsoft.com>
* [Search] Add API version to tspconfig * Add small comment
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
#43710) * Mitigate Python SDK breaking changes for azure-mgmt-managednetworkfabric * Update client.tsp
* update config * update * update * update
* chore: updates @azure-tools/openai-typespec package to its latest version chore: updates openai typespec definitions to 1.18 chore: switches to save exact command * docs: add READMEs for Foundry openapi3 v1 and virtual-public-preview Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> fix: rename Foundry openapi3 README.md to lowercase readme.md for Avocado Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * chore: add BYOT and MCPHTTP to ai-foundry cspell words Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * chore: refreshes generated files * Revert "docs: add READMEs for Foundry openapi3 v1 and virtual-public-preview" This reverts commit f79aed2. * chore: updates openai typespec definitions to 1.19 --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Member
Author
|
manually merged directly in the target branch |
This file contains hidden or 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
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.
azure-sdk-automation[bot]([protected-files] Allow userazure-sdk-automation[bot]#43152)ClientRequestIdHeaderand Go Customizations #43146)azure_storage_queuetypespec changes ([Storage]azure_storage_queuetypespec changes #43001)microsofttoMicrosoft- Microsoft.AlertsManagement #43246)microsofttoMicrosoft- Microsoft.Automation #43248)microsofttoMicrosoft- Microsoft.ApiManagement #43247)microsofttoMicrosoft- Microsoft.DataFactory #43249)WebApplicationFirewallPolicyclient name & add finalResult (Fix CDNWebApplicationFirewallPolicyclient name & add finalResult #43241)microsofttoMicrosoft- Microsoft.RecoveryServices #43253)TSP-ARRAY-IDENTIFIERSreview rule: ban@extension("x-ms-identifiers", ...)in TypeSpec; require@key/@identifiers#43273)