Updating stable release branch#41047
Open
jeremyfrosti wants to merge 2634 commits into
Open
Conversation
jeremyfrosti
requested review from
a team,
MaryGao,
benbp,
live1206,
maririos,
mikeharder,
praveenkuttappan,
pshao25,
raych1,
solankisamir and
weshaggard
as code owners
Next Steps to MergeNext steps that must be taken to merge this PR:
Comment generated by summarize-checks workflow run. |
github-actions
Bot
added
resource-manager
RPaaS
SuppressionReviewRequired
TypeSpec
Contributor
|
You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool. What Enabling Code Scanning Means:
For more information about GitHub Code Scanning, check out the documentation. |
* update * update
* update * update * update * update * update * update
* update * update * update * update * update * update * update * update * update * update * update
* Added changes for commvault in public repo
* Removed a file
* fix: migrate liftrcommvault TypeSpec project to folder structure v2
Move TypeSpec project from specification/liftrcommvault/Commvault.ContentStore.Management/
to specification/liftrcommvault/resource-manager/Commvault.ContentStore/ContentStore.Management/
to comply with folder structure v2 requirement.
- Moved main.tsp, tspconfig.yaml, examples/ to v2 location
- Moved generated preview OpenAPI files to match new location
- Updated tspconfig.yaml: emitter-output-dir now points to {project-root}
- Updated resource-manager/readme.md input-file paths
- Deleted old non-v2 Commvault.ContentStore.Management folder
* Revert "fix: migrate liftrcommvault TypeSpec project to folder structure v2"
This reverts commit 69e4146.
* Removed a files
* Revert "Removed a files"
This reverts commit 91dbdd2.
* Added changes for suppression
* Added changes for suppression
* Added changes for suppression
* Fix SDK compilation errors: make read-only ProtectionGroup fields optional and use proper update model for CloudAccount
* Revert "Fix SDK compilation errors: make read-only ProtectionGroup fields optional and use proper update model for CloudAccount"
This reverts commit 3dd10f5.
* Updated response code for stop backup
* Updated response code for stop backup
* Updated response code for stop backup
* Formated the tsp file
* Fixed the SDK issue
* Format main.tsp
* Fix PatchBodyParametersSchema: use implicit optionality for CloudAccount PATCH
* Updated namespaces
---------
Co-authored-by: Saurav Raj <sauravraj@microsoft.com>
…or .NET deny assignment PUT/DELETE (#44165) Adds a .NET-only AutoRest tag identical to package-2022-04-01 but swapping the deny assignment input file to preview/2024-07-01-preview, which includes the DenyAssignments_CreateOrUpdate (PUT) and DenyAssignments_Delete (DELETE) operations. Co-authored-by: Jonathan Ruttle <jruttle@microsoft.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…44132) The Azure.ResourceManager.MongoDBAtlas .NET SDK requires generated resource types to use the MongoDBAtlas* prefix. Without these client renames the generator emits Project/Cluster/ProjectProperties/ClusterProperties/ClusterTier unprefixed, violating the management-plane package naming convention and forcing [CodeGenType] customization workarounds in the SDK. These decorators fix the naming at the spec source, consistent with the existing OrganizationResource rename above. Related SDK PR: Azure/azure-sdk-for-net#60084
…44099) * Initial plan * Harden ARM API Reviewer↔Critic interaction protocol Co-authored-by: ravimeda <12752450+ravimeda@users.noreply.github.com> * Address code review feedback: rename eval stimulus, fix protocol FAIL catalog description Co-authored-by: ravimeda <12752450+ravimeda@users.noreply.github.com> * Apply prettier formatting to agent and skill files Co-authored-by: ravimeda <12752450+ravimeda@users.noreply.github.com> --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: ravimeda <12752450+ravimeda@users.noreply.github.com>
* Update tsp-client Node engine requirement to >=22.0.0 * update package lock json --------- Co-authored-by: Minh-Anh Phan <111523473+minhanh-phan@users.noreply.github.com>
…meter and response enum casing (#44553) * Document Translation: fix getSupportedFormats 'type' parameter and response enum casing The 'type' query parameter on GET /document/formats is required by the service (it returns 404 when omitted and accepts an empty 'type='), so mark it required across all versions. The service also returns PascalCase 'Document'/'Glossary' in the FileFormat.type response, so correct the FileFormatType enum values to match. The query parameter is case-insensitive and the enum is extensible, so this remains backward-compatible. These correct long-standing spec inaccuracies; the actual wire contract is unchanged. * Migrate Document Translation JS emitter from RLC to modular (DFG) - Remove is-modular-library: false - Rename package @azure-rest/ai-translation-document -> @azure/ai-translation-document - Update output dir to drop -rest suffix * Document Translation: fix glossary multipart type to HttpPart<bytes>[] The glossary form field was declared as HttpPart<bytes[]> (array inside the part), which models a single multipart part containing a base64-encoded JSON array (format: byte, contentType: application/json). The service actually accepts multiple binary glossary file parts. Change to HttpPart<bytes>[] so each glossary file is a separate binary part (format: binary). The checked-in Swagger (openapi.json) is unchanged, but generated SDKs now correctly model multi-file binary upload. --------- Co-authored-by: Jiarui Guo <jiarguo@microsoft.com>
* Refactor devcenter folder structure to comply with Azure Guidelines * Fixed all common-types references, updated readme.md, tspconfig.yaml, suppressions.yaml * Fix API version mismatch CI error * Add branch file for missingTag * test skipRLC * disable dataplane sdk generate for js * revert * Update archetype-spec-gen-sdk.yml * update * update * update * update * fix * update * add suppress * Fix prettier formatting for devcenter spec files --------- Co-authored-by: Kyle Zhang <v-zhanh@microsoft.com> Co-authored-by: Jiao Di (MSFT) <v-jiaodi@microsoft.com> Co-authored-by: Jiao Di (MSFT) <80496810+v-jiaodi@users.noreply.github.com> Co-authored-by: Qiaoqiao Zhang <qiaozha@microsoft.com>
#42890) * Add 2026-04-01-preview API version for Microsoft.Cdn RP for public preview (Multilevel waf feature) * Add origin authentication token destination header Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Update token destination header name Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Add mTLS, url signing API definitions back to 2026-04-01-preview * Regenerate openapi.json and examples for 2026-04-01-preview Include mTLS and AfdUrlSigning definitions in generated output. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * adding edge action & AFD rule association back --------- Co-authored-by: Jinqiang Ding <jiding@microsoft.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: Jessica Li <jessicl@microsoft.com> Co-authored-by: Zhe Feng <zhefeng@microsoft.com>
* Remove suppressions for client import * Remove stale TypeSpecValidation suppressions for deleted paths * Narrow SdkTspConfigValidation suppressions to failing sub-rules; drop dead ExtraSwagger entries (fabric, batch)
#43548) * Add Versions enum and decorate preview-only resource files * Decorate preview-only declarations in models.tsp * Fix Entity versioning * Versioning models.tsp * Versioning AlertRule, Bookmark, DataConnector, routes, Relation * Add 'using TypeSpec.Versioning;' to files using @added * Add openapi.json + examples for 2025-09-01 and 2025-10-01-preview * Switch stable/2025-09-01 to single openapi.json; delete split files and common/ * Add tag package-preview-2025-10-01 to readme * Revert AATP/MCAS/MDATP/MSTI model names to PascalCase to fix casing-style lint * Run tsp format (remove trailing blank line in Entity.tsp) * Fix api-version in 2025-10-01-preview examples * Restore stable/2025-09-01/common/1.0/types.json (pre-existing orphan) * Fix Incidents_RunPlaybook 204 response: remove unknown body * Revert "Fix Incidents_RunPlaybook 204 response: remove unknown body" This reverts commit 4d3220a. * Add 204 body to stable Incidents_RunPlaybook example to match spec * Preserve SecurityInsights schema compatibility Co-authored-by: AdiMegid <277261726+AdiMegid@users.noreply.github.com> * Revert last commit (TSP schema changes) * Fix Watchlist headers * Add 204 body to Incidents_RunPlaybook example to match schema * fix headers * fix required status changes for Package/Template/ScheduledAlertRule models - Move required fields from PackageBaseProperties to PackageProperties and ProductPackageProperties - Move required fields from TemplateBaseProperties to TemplateProperties and ProductTemplateProperties - Restore ScheduledAlertRuleCommonProperties fields as required (no @madeOptional) - Remove unused stable/2025-09-01/common folder * fix required status for ScheduledAlertRuleCommonProperties and Page<T> models * fix x-ms-enum names for flag and triggerWhen * fix x-ms-enum names * fix x-ms-enum names for (MetadataDependencyOperator, PullRequestState, WatchlistProvisioningState, JobProvisioningState) * add readOnly to nextLink properties * restore package base props to PackageBaseProperties * Revert "restore package base props to PackageBaseProperties" * rename metadataDependencies kind enum to metadataKind * revert metadataKind rename * revert required status changes for Package/Template * fix typeSpec validation * fix Java SDK build: remove ScheduledAlertRuleProperties required redeclarations * Remove redundant supressions * remove supress * revert camelcase to pascalcase * fix PascalCase * Fix ineffective LintDiff suppressions in SecurityInsights readme The package-preview-2025-10-01, package-2025-09-01, and package-preview-2025-07-01 tags each compile to a single bundled openapi.json, but their suppressions used 'from: <logical-file>.json' (dataConnectors.json, Entities.json, etc.). Autorest matches suppression 'from' via document.endsWith(from), so those never matched the bundled openapi.json and the suppressions were silently inert. Set 'from: openapi.json' and add scoped 'where:' clauses targeting each violation's exact JSONPath. Also complete the stable 2025-09-01 coverage so it lints clean and stays consistent with the preview tags. Verified with the ARM linter: all targeted violations now suppressed. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Adi Megidish <t-amegidish@microsoft.com> Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: AdiMegid <277261726+AdiMegid@users.noreply.github.com> Co-authored-by: Guy Wilf Shukrun <gwilfshukrun@microsoft.com> Co-authored-by: Guy Wilf Shukrun <guywilfshukrun@gmail.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Add ContainerServiceSafeguards CSharp mgmt emitter Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * fix JS generation failure * Revert "Add ContainerServiceSafeguards CSharp mgmt emitter" This reverts commit 4771a7b. * Update client.tsp --------- Co-authored-by: Wei Hu <live1206@gmail.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Add ContainerServiceSafeguards CSharp mgmt emitter Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Apply suggestion from @JialinHuang803 --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: JialinHuang803 <139532647+JialinHuang803@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: c9b8c6af-4818-4111-b275-0975dd81e2a7 Co-authored-by: Yulin Li <yulili@microsoft.com>
Java (typespec-java) was included in the flattenProperty scope for MongoIndex.key, which renamed the public key()/withKey(MongoIndexKeys) API to a flattened keys()/withKeys(List<String>) and moved MongoIndexKeys to the implementation package. Add !java to the scope to preserve the existing Java public API. Copilot-Session: b3fffb85-d710-47f5-b9ba-687c505134ca Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Dapeng Zhang <dapzhang@microsoft.com>
…43168) * Add MachineLearningServices preview API version 2026-03-15-preview swagger * Add Ray distribution type to MachineLearningServices 2026-03-15-preview (#42127) * Expand LintDiff suppressions for 2026-03-15-preview tag The default tag shifted from preview (2026-01-15-preview) to stable (2026-03-01) after the stable merge. LintDiff now compares stable vs preview baseline, surfacing pre-existing violations that were previously masked by preview-to-preview comparison. All suppressed violations are verified pre-existing in the 2026-01-15-preview swagger. Global suppressions (matching stable tag approach): DeleteResponseCodes, ProvisioningStateMustBeReadOnly, GetCollectionOnlyHasValueAndNextLink, PostResponseCodes, PatchIdentityProperty, PatchBodyParametersSchema, PathForResourceAction, ResourceNameRestriction, CollectionObjectPropertiesNaming, ProvisioningStateSpecifiedForLROPut, PatchResponseCodes, PutResponseCodes, XmsPageableForListCalls. Targeted suppressions with WHERE clauses: - AvoidAdditionalProperties: 78 paths across 10 logical groups (dictionary types for env vars, job I/O, metadata, Spark config, monitoring signals, K8s infra, traffic routing, model registries, polymorphic models, and diagnostics) - XMSSecretInResponse: 7 paths (compute secrets, datastore creds) - GuidUsage: 1 path (Azure.Core.uuid TypeSpec built-in) - UnSupportedPatchProperties: 1 path (managedNetworks PATCH) * fix: revert default tag to stable package-2026-03-01 The default tag must remain the latest stable version. Preview tags exist as opt-in (--tag=package-preview-2026-03-15-preview). Changing the default to a preview tag caused Avocado MISSING_APIS_IN_DEFAULT_TAG (30 deprecated API paths not in preview spec) and LintDiff to report 527 false-positive new violations from cross-file comparison. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Fix ParametersSchemaAsTypeObject suppression paths to match violation jsonpath The suppression 'where' clauses were using dot notation (parameters.5) without the full path to the violation location. The Spectral validator reports violations at parameters[N].schema.type, so suppressions must use bracket notation with the full path (parameters[5].schema.type) to match correctly. This aligns with the working format used in older preview tags (2025-10-01-preview, 2025-07, etc.). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Add MachineLearningServices preview API version 2026-05-15-preview Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Wire up 2026-05-15-preview source: enum, preview re-promotions, readme tag The prior commit added only the generated 2026-05-15-preview swagger output without the TypeSpec source that defines it. This commit supplies the missing source and rebases onto the merged stable 2026-05-01 (#42547): - Add v2026_05_15_preview to the MLS Versions enum (main.tsp) - Add @added(Versions.v2026_05_15_preview) after each of the 76 @removed(Versions.v2026_05_01) decorators, re-promoting into the new preview the preview-only features gated out of stable 2026-05-01 (suppress -> promote -> suppress -> promote chain) - Add package-preview-2026-05-15-preview readme tag (newest-by-date; default tag stays package-2026-05-01) with carried-forward suppressions - Regenerate openapi.json (also fixes a missing request body on OnlineEndpoints_CreateOrUpdate present in the orphaned output) Verified: 2026-05-15-preview is content-identical to 2026-03-15-preview (752 defs / 174 paths, zero missing/extra; normalized openapi diff = 0; 323/323 examples, no orphans/dangling refs). main.tsp and client.tsp compile. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Suppress AvoidAnonymousParameter for InferenceEndpoints update in 2026-05-15-preview InferenceEndpoints update uses a free-form custom patch envelope (Record<unknown>), pre-existing and unchanged since 2026-01-15-preview. LintDiff flags it only because it compares this preview tag against the stable base (2026-05-01), which excludes the preview-only InferenceEndpoint resource. Verified locally with lint-diff: the single must-fix AvoidAnonymousParameter error is cleared (0 errors introduced; warnings only). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Re-trigger CI checks Empty commit to refresh the stale spec - api-doc-preview check. Build #20260630.72 failed only because the shared azuresdk-github-pat exceeded the new Microsoft Open Source enterprise 8-day classic-PAT lifetime limit (HTTP 403 on the pre-checkout Set PR status step), which skipped checkout and cascaded to unrelated errors. The token has since been rotated; a fresh run will pass. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: ahyerman <10575616+ahyerman@users.noreply.github.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Add examples and property * Compile * tsp format * Address feedback --------- Co-authored-by: Celina Zhao <zhaocelina@microsoft.com>
* [AppService] [Web] Add stable 2026-07-15 with AppServicePlan startWebApps/stopWebApps (#43926) * [Web] Add stable 2026-07-15 with AppServicePlan startWebApps/stopWebApps actions * [Web] Address ARM review: use NoContentResponse (204) for start/stopWebApps --------- Co-authored-by: Kray Cuellar <krayc@microsoft.com> * Add Site maintenance feature to Microsoft websites (#44020) * Added Site maintenance feature to Microsoft websites * Removed version annotation * Undo trimTrailingWhitespace * Fix merge conficts and fix the CI build * Remove extra leading space * Added misssing @added annotations * correct siteConfig response example * [Microsoft.Web] Add go as a valid Function App runtime (2026-07-15) (#43830) * Add go to Function App RuntimeName enum in AppService stable 2026-03-15 OpenAPI spec * Add go runtime to AppService 2026-03-15 spec Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Format AppService RuntimeName after go addition Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * AppService: keep only stable/2026-07-15/openapi.json and revert 2026-03-15/models.tsp changes * AppService 2026-07-15: remove orphan ErrorPage additions and fix maintenanceEnabled wording * restore Go runtime in 2026-03-15, and retain ARM review fixes * AppService: sync 2026-07-15 RuntimeName OpenAPI with TypeSpec generation (include go) * AppService: move RuntimeName.go introduction to 2026-07-15 and regenerate 2026-03-15 OpenAPI --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Kray <kray.cuellar@gmail.com> Co-authored-by: Kray Cuellar <krayc@microsoft.com> Co-authored-by: Carlos Soto Pérez <csotoperez@microsoft.com> Co-authored-by: Harshitha Vegaraju <24836340+harshivcodes@users.noreply.github.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
…l to .github/arm-leases/durabletask/Microsoft.DurableTask/DurableTask/lease.yaml (#44627)
* Simplified pipeline variables for auto-release * Fixed review feedback --------- Co-authored-by: Ray Chen <raychen@microsoft.com>
* Introduce 2026-06-01-preview * fix typesec validation error * Format TypeSpec files for AzureFleet * add Karpenter to cspell * Remove "karpenter" word and add extra comments --------- Co-authored-by: Nithin Ramachandrappa (from Dev Box) <nithinram@microsoft.com>
* Base version
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* New API Version 2026-06-01-preview
Rename Migration_* operationIds to Migrations_* by removing the back-compatible clientLocation overrides; regenerated all affected API versions from TypeSpec.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Version-scope Migrations interface rename to 2026-06-01-preview
The Migrations TypeSpec interface was pluralized at some point but
older preview API versions had already shipped with singular
Migration_{List,Get,Start,Cancel} operationIds (with Migrations_Validate
added later already in plural form). Regenerating those older versions
with plural operationIds would break the shipped contract.
Use @renamedFrom(Versions.v2026_06_01_preview, "Migration") on the
interface so the compiler emits the original singular Migration_*
operationIds for 2025-08-01-preview, 2026-02-01-preview and
2026-05-01-preview, and only the new 2026-06-01-preview gets the
plural Migrations_* form.
Pin validate's operationId to "Migrations_Validate" so its already-
shipped plural spelling is preserved in every version regardless of
the interface rename.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Suppress no-openapi rule on Migrations.validate operationId override
The azure-core linter flags any explicit @operationid as unusual.
Suppress it here because pinning validate to 'Migrations_Validate'
in every version is required to keep the shipped operationId stable
while the interface itself is renamed from 'Migration' to 'Migrations'
at 2026-06-01-preview via @renamedFrom.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Rename Migrations tag to Migration in older previews
With @renamedFrom(Versions.v2026_06_01_preview, "Migration") on the
interface, tsp compile now emits "tags": ["Migration"] and the
top-level tag entry {"name": "Migration"} for the older-version
swaggers to match the singular Migration_* operationId prefix.
Update the committed JSONs so "tsp compile" produces a clean diff.
Tags only drive swagger doc grouping, no SDK contract impact.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Reformat back-compatible.tsp to satisfy tsp format
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Keep 'Migrations' tag on older API versions using @tag
Revert the tag renames in the older-version swagger JSONs and instead
force the emitted OpenAPI tag to 'Migrations' via @tag on the interface.
This preserves the older shipped swagger contracts unchanged: their
operationIds keep the singular Migration_* prefix (via @renamedFrom)
and their tags keep the plural 'Migrations' value.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Mariano Rico <marianor@microsoft.com>
* Update tspconfig.yaml * Update client.tsp * Update client.tsp * Update client.tsp * Update client.tsp * Update client.tsp
* Update client.tsp * Update tspconfig.yaml * Update client.tsp
* Update tspconfig.yaml * Update tspconfig.yaml
* Prepare specs for no-url-suffix lint rule Add #suppress directives and @@clientName URL-to-Uri customizations across affected TypeSpec specs in preparation for the no-url-suffix lint rule. Squashed rebase of PR #43818 onto latest main; resolved the liftrmongodb client.tsp conflict by keeping both the Project/Cluster renames from main and the redirectUrl->redirectUri rename. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Remove duplicate csharp-no-url-suffix suppressions Each flagged property had the identical #suppress line written twice. Collapse the 32 exact-duplicate suppressions (across 16 files) to a single suppression per property. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Remove non-adjacent duplicate csharp-no-url-suffix suppressions 6 properties (botservice x4, cost-management x2) had csharp-no-url-suffix suppressed twice with a pre-existing casing-style suppress between the two, so they were non-adjacent and missed by the first dedup pass. Collapse to a single csharp-no-url-suffix suppression per property. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Move no-url-suffix to client-sdk ruleset: extend it for client-SDK specs, drop suppressions elsewhere Step 2 of the no-url-suffix rollout. The csharp-no-url-suffix rule now lives in the new client-sdk ruleset (typespec-azure #4541), so: (1) add the client-sdk ruleset to linter.extends in all 349 tspconfigs configured to emit a client SDK, (2) remove the 60 now-dead suppressions from 25 non-client projects, (3) refresh the @4541 lockfile pin to build .1516 which contains the moved rule. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Pin typespec-azure deps to immutable commit URL (fix npm ci EINTEGRITY) The @4541 pkg.pr.new moving tag repacks with a new hash on each fetch, so npm ci fails with EINTEGRITY (lockfile integrity != freshly downloaded tarball). Pin both @azure-tools/typespec-azure-rulesets and @azure-tools/typespec-client-generator-core to the immutable commit-specific URL @97378df6, which serves a byte-stable tarball. Integrity values are unchanged (they already match the commit artifact). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Restore suppressions for shared sub-models consumed by client-SDK parents; fix cloudhealth tspconfig format Step 2 removed csharp-no-url-suffix suppressions from sub-projects whose own tspconfig is non-client, but whose models are compiled by a client-SDK parent (applicationinsights, compute/Compute, monitor/Insights, network/Network). With client-sdk added to those parents, the rule fired on the now-unsuppressed *Url properties (50 TSV errors). Restore the 25 suppressions in the 7 shared model files. Also convert cloudhealth linter.extends from inline array to block list (prettier/tsv Format rule). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Bump typespec-azure deps to @4541 build .1525 (includes #4730 override fix) Repin to the immutable commit URL @30de6998 (build 0.70.0-pr-4541.1525), which includes tadelesh's #4730 @OverRide regression fix. With #4730, the override-parameters-mismatch errors drop to 37 (the genuine 'override param dropped @path' cases across 11 projects); the false-positive regressions are fixed. Demonstrates #4730 reduces but does not fully clear the override errors without spec-side @path additions. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Use released 0.69.2 for tcgc/rulesets/resource-manager (drop pkg.pr.new pin) Now that @azure-tools/typespec-client-generator-core, typespec-azure-rulesets, and typespec-azure-resource-manager 0.69.2 are published (with the client-sdk ruleset and the #4730 override fix), switch off the pkg.pr.new build pins. Also drop the legacy-peer-deps=true .npmrc workaround since 0.69.2 peers resolve cleanly. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Keep resource-manager at 0.69.1; suppress 11 url-suffix violations unmasked by 0.69.2 Revert typespec-azure-resource-manager to 0.69.1 (keep tcgc + rulesets at 0.69.2). resource-manager 0.69.2 changes CommonTypes emission (external \ -> inlined definitions), which regenerates swagger for RM projects (e.g. devcenter, maps) and is unrelated to the url-suffix rule. The rulesets 0.69.2 peer on resource-manager ^0.69.2 is only an npm warning. Add csharp-no-url-suffix suppressions for 11 properties in cognitiveservices, policyinsights, and security. These were previously hidden because those projects had compile-blocking override-parameters-mismatch errors; 0.69.2's override fix unmasked them. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Add npm override so rulesets 0.69.2 accepts resource-manager 0.69.1 npm ci uses strict peer resolution and errored with ERESOLVE because typespec-azure-rulesets@0.69.2 has a peer of resource-manager@^0.69.2 while we deliberately keep resource-manager at 0.69.1 (to avoid CommonTypes swagger regeneration). A surgical overrides entry satisfies the peer without adding legacy-peer-deps to .npmrc. The resolved tree is unchanged (rm stays 0.69.1), so package-lock.json needs no update. Verified pm ci no longer ERESOLVEs. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Bump typespec-azure-resource-manager to 0.69.2 and regenerate affected swagger Drop the npm override and bump resource-manager 0.69.1 -> 0.69.2 so rulesets 0.69.2's peer is satisfied directly. rm 0.69.2 includes typespec-azure#4627, which emits the CustomerManagedKeyEncryption and Encryption common-types inline instead of as external \s. Regenerated the impacted swagger accordingly: devcenter DevCenterRP.json (3 API versions) and maps maps-management.json. This is the alternative to keeping rm at 0.69.1 behind an override; posting it so we can decide whether to take the rm 0.69.2 bump (with this swagger change) or revert to the override. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Suppress 5 url-suffix violations in developerhub (surfaced after merge) The latest main merge brought developerhub changes with authURL/prURL/ workflowRunURL properties. Add csharp-no-url-suffix suppressions so the client-sdk ruleset passes TSV. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> * Remove client-sdk ruleset from 7 legacy-emitter data-plane services These services generate their .NET SDK with the legacy @azure-tools/typespec-csharp emitter, which pins typespec-azure-rulesets 0.61.0 and therefore lacks the client-sdk ruleset - causing 'unknown-rule-set: client-sdk' in .NET SDK Validation. Remove client-sdk from their linter.extends until each migrates to the @azure-typespec/http-client-csharp emitter (rulesets 0.69.2), at which point it can be re-enabled per-service. Services: attestation, confidentialledger (ConfidentialLedger + ConfidentialLedgerIdentity), containerregistry, loadtestservice/playwright, webpubsub, apicenter. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: Razvan Badea <156206747+razvanbadea-msft@users.noreply.github.com>
…012/AZC0030) (#44615) Rename generated model/enum types for the C# SDK only via @clientName so the Azure.Security.ConfidentialLedger library follows Azure SDK for .NET naming guidelines, removing the need to suppress analyzers AZC0012 and AZC0030. Scope is limited to "csharp" so the REST/wire contract and the already generated JavaScript, Python and Java SDKs are unchanged. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Adding new API version 2026-05-01 * Adding changes to API version 2026-05-01 and 2026-05-15-preview * Format tsp files * Added rename tag for usageThreshold20250901 * Added rename tag for sizeOld on capacity pool tsp * Added rename tag for usageThreshold in VolumeProperties * Remove unintended decorators for usageThreshold in VolumeProperties * Update tags for updatePrevious in NetappAccount.tsp * Update tags for sizeOld in PoolPatchProperties * Adding Deprecation message for subvolumes related models and properties * Update version in tspconfig.yaml * Correct versioning issue with NetAppAccountPatchStable
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.
ARM (Control Plane) API Specification Update Pull Request
Tip
Overwhelmed by all this guidance? See the
Getting helpsection at the bottom of this PR description.PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.
Purpose of this PR
What's the purpose of this PR? Check the specific option that applies. This is mandatory!
Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.
Additional information
Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the
Generated ApiViewcomment added to this PR. You can use ApiView to show API versions diff.Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
suppressions guide to get approval.
Getting help
Purpose of this PRandDue diligence checklist.write accessper aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositoriesNext Steps to Mergecomment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.and https://aka.ms/ci-fix.
queuedstate, please add a comment with contents/azp run.This should result in a new comment denoting a
PR validation pipelinehas started and the checks should be updated after few minutes.