Skip to content

Comments

Upgrade to TypeSpec 0.66#32992

Merged
mikeharder merged 11 commits intomainfrom
upgrade/typespec-0.66
Mar 4, 2025
Merged

Upgrade to TypeSpec 0.66#32992
mikeharder merged 11 commits intomainfrom
upgrade/typespec-0.66

Conversation

@timotheeguerin
Copy link
Member

No description provided.

mikeharder and others added 11 commits February 27, 2025 19:35
* update `@OpenAPI.extension` usage to value syntax

* additional spec fixes

---------

Co-authored-by: Christopher Radek <Christopher.Radek@microsoft.com>
* Replace x-ms-identifiers

* x-ms-emitters clean up

* fix differences after sanity check

* stanby scenario

* stanby scenario

* revert the ones that are causing problems in .NET

* Update identifiers

* two more scenarios of extension

* one more scenarios of extension
…y modifiers. (#32952)

* Replace all string visibility modifiers with Lifecycle.

* Format specs

* fix communication messages

* link local packages

* Fix communication.messages

* Update Chaos.Management parameter visibility use

* Replace @parameterVisibility with patch option in operation explicitly labeled PATCH

* Replace all @parameterVisibility on ARM Patch operations with implicitOptionality: false

* ScVmm: use Lifecycle.Read instead of 'read' in augmentation

* Keyvault: remove redundant @patch

* connectedcache: Use Lifecycle instead of strings in augmentation

* app: change visibility of SessionResourceFile.name to be more restricted to satisfy lint rule

* Use web deps

* Reset package.json to use next publications.

* appcomplianceautomation: restore usings incorrectly removed

* batch: remove errant model expr augments

* standbypool: update visibility to Lifecycle

---------

Co-authored-by: Will Temple <will@wtemple.net>
@openapi-pipeline-app
Copy link

openapi-pipeline-app bot commented Mar 4, 2025

Next Steps to Merge

Next steps that must be taken to merge this PR:
  • ❌ This is the public specs repo main branch 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, add PublishToCustomers label to your PR.
    Otherwise, retarget this PR onto a feature branch, i.e. with prefix release- (see aka.ms/azsdk/api-versions#release--branches).
  • ❌ This PR is in purview of the ARM review (label: ARMReview). This PR must get ARMSignedOff label from an ARM reviewer.
    This PR is awaiting ARM reviewer feedback (label: WaitForARMFeedback).
    To learn when this PR will get reviewed, see ARM review queue at aka.ms/azsdk/pr-arm-review
    For details of the ARM review, see aka.ms/azsdk/pr-arm-review
  • ❌ The required check named Protected Files has 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

This was referenced Mar 4, 2025
@mikeharder mikeharder merged commit a0dc634 into main Mar 4, 2025
45 of 54 checks passed
@mikeharder mikeharder deleted the upgrade/typespec-0.66 branch March 4, 2025 22:50
pjpatel12 pushed a commit to pjpatel12/azure-rest-api-specs that referenced this pull request Apr 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ARMReview BreakingChange-Go-Sdk BreakingChange-JavaScript-Sdk BreakingChange-Python-Sdk ReadyForApiTest <valid label in PR review process>add this label when swagger and service APIs are ready for test resource-manager RPaaS TypeSpec Authored with TypeSpec WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants