Skip to content
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

[@azure-tools/azure-http-specs] - Rollout the azure http specs package #1753

Merged
merged 3 commits into from
Oct 29, 2024

Conversation

sarangan12
Copy link
Contributor

This is the azure specific counter part of the PR microsoft/typespec#4836. In this PR, the azure-http-specs package is being rolled out.

Please review and approve the PR. Thanks

pnpm-lock.yaml Outdated Show resolved Hide resolved
@sarangan12 sarangan12 force-pushed the RollOutAzureHttpSpecs branch from 675ae35 to c86714a Compare October 29, 2024 17:38
@timotheeguerin timotheeguerin added this pull request to the merge queue Oct 29, 2024
Merged via the queue into Azure:main with commit 1f36182 Oct 29, 2024
18 checks passed
github-merge-queue bot pushed a commit to microsoft/typespec that referenced this pull request Oct 29, 2024
Related to Azure/typespec-azure#1753 , I am
fixing the test script. Refer
Azure/typespec-azure#1753 (comment)
for more details.

Please review and approve the PR. Thanks
swatkatz pushed a commit to swatkatz/typespec that referenced this pull request Nov 5, 2024
Related to Azure/typespec-azure#1753 , I am
fixing the test script. Refer
Azure/typespec-azure#1753 (comment)
for more details.

Please review and approve the PR. Thanks
markcowl pushed a commit to markcowl/typespec-azure that referenced this pull request Dec 5, 2024
Azure#1753)

This is the azure specific counter part of the PR
microsoft/typespec#4836. In this PR, the
`azure-http-specs` package is being rolled out.

Please review and approve the PR. Thanks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants