-
Notifications
You must be signed in to change notification settings - Fork 5.1k
Bump azure generator #53833
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
Bump azure generator #53833
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR bumps the Azure Management Generator (@azure-typespec/http-client-csharp) from version 1.0.0-alpha.20251022.3 to 1.0.0-alpha.20251108.1, along with its underlying dependency @typespec/http-client-csharp from 1.0.0-alpha.20251022.4 to 1.0.0-alpha.20251107.3.
Key Changes:
- Updated Azure generator dependency to Nov 8, 2025 release
- Updated underlying TypeSpec C# generator to Nov 7, 2025 release
- Synchronized version reference in build properties file
Reviewed Changes
Copilot reviewed 2 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| eng/packages/http-client-csharp-mgmt/package.json | Updated main dependency @azure-typespec/http-client-csharp to 1.0.0-alpha.20251108.1 and devDependency @typespec/http-client-csharp to 1.0.0-alpha.20251107.3 |
| eng/packages/http-client-csharp-mgmt/package-lock.json | Updated lockfile to reflect new package versions and their transitive dependencies with corresponding integrity hashes |
| eng/Packages.Data.props | Updated AzureGeneratorVersion property to 1.0.0-alpha.20251108.1 to match the new generator version |
Files not reviewed (1)
- eng/packages/http-client-csharp-mgmt/package-lock.json: Language not supported
|
/check-enforcer override |
Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.