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 Plugin] Is there a way we could ensure the version number of npm package and the version number of dll the same? #47912

Open
ArcturusZhang opened this issue Jan 21, 2025 · 0 comments
Labels
Client This issue points to a problem in the data-plane of the library. CodeGen Issues that relate to code generation

Comments

@ArcturusZhang
Copy link
Member

Currently, when building the azure plugin, we need two dependencies: npm package (the emitter), MGC plugin (the dll).
They have their own version numbers, but they are written in two different places:
npm package's version is written in package.json:

"@typespec/http-client-csharp": "0.1.9-alpha.20241219.2"

dll package's version is written in Package.Data.props:
<PackageReference Update="Microsoft.Generator.CSharp.ClientModel" Version="1.0.0-alpha.20250117.1" />

@ArcturusZhang ArcturusZhang added the CodeGen Issues that relate to code generation label Jan 21, 2025
@jsquire jsquire added the Client This issue points to a problem in the data-plane of the library. label Jan 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Client This issue points to a problem in the data-plane of the library. CodeGen Issues that relate to code generation
Projects
None yet
Development

No branches or pull requests

2 participants