Skip to content

Succeeded with Issues: Update @typespec/http-client-csharp to 1.0.0-alpha.20260320.2#1044

Open
github-actions[bot] wants to merge 2 commits intomainfrom
typespec/update-http-client-csharp-1.0.0-alpha.20260320.2
Open

Succeeded with Issues: Update @typespec/http-client-csharp to 1.0.0-alpha.20260320.2#1044
github-actions[bot] wants to merge 2 commits intomainfrom
typespec/update-http-client-csharp-1.0.0-alpha.20260320.2

Conversation

@github-actions
Copy link
Contributor

This PR automatically updates the TypeSpec HTTP client C# generator version and regenerates the SDK code.

Changes

  • Updated @typespec/http-client-csharp from 1.0.0-alpha.20260306.4 to 1.0.0-alpha.20260320.2
  • Updated Microsoft.TypeSpec.Generator.ClientModel from 1.0.0-alpha.20260306.4 to 1.0.0-alpha.20260320.2
  • Updated OpenAI plugin package.json file
  • Updated Directory.Packages.props with new generator package version
  • Regenerated OpenAI SDK code using the new generator version
  • Updated centrally managed package-lock.json file with new dependency versions

Details

Testing

Please run the existing test suites to ensure the generated code works correctly:

  • Build and test the OpenAI SDK
  • Verify API compatibility and functionality

Notes

This PR was created automatically by the Update TypeSpec Generator Version workflow. The workflow runs weekly and when manually triggered to keep the generator version current with the latest TypeSpec improvements and fixes.

  • Action Run
    If there are any issues with the generated code, please review the TypeSpec release notes for breaking changes or new features that may require manual adjustments.

- Updated @typespec/http-client-csharp from 1.0.0-alpha.20260306.4 to 1.0.0-alpha.20260320.2
- Updated Microsoft.TypeSpec.Generator.ClientModel from 1.0.0-alpha.20260306.4 to 1.0.0-alpha.20260320.2
- Regenerated OpenAI SDK code with new generator version
- Updated centrally managed package-lock.json file with new dependency versions
@MaiLinhP
Copy link
Collaborator

MaiLinhP commented Mar 24, 2026

@joseharriaga I talked to Josh about the duplicated client name errors, and he suggested to check with newest version as there were a lot of changes with tcgc last week, so I moved to this one. But it seems like it still persists, in that for the same union across different models, the generator used to rename them per client to avoid collision. But it's now no longer doing so to avoid duplication but not properly handling the collision. So the fix right now is still to add images.client.tsp and images.models.tsp. I could also try to chase down why there's this change in how the generator handles this, and how to properly handle collision, but it'll just take some time :)

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