Skip to content

Update UnbrandedGeneratorVersion to 1.0.0-alpha.20260218.5#56330

Open
azure-sdk wants to merge 4 commits intomainfrom
typespec/update-http-client-1.0.0-alpha.20260218.5
Open

Update UnbrandedGeneratorVersion to 1.0.0-alpha.20260218.5#56330
azure-sdk wants to merge 4 commits intomainfrom
typespec/update-http-client-1.0.0-alpha.20260218.5

Conversation

@azure-sdk
Copy link
Collaborator

This PR updates the UnbrandedGeneratorVersion property in eng/Packages.Data.props and the @typespec/http-client-csharp dependency in eng/packages/http-client-csharp/package.json to version 1.0.0-alpha.20260218.5.

Details

Changes

  • Updated eng/Packages.Data.props UnbrandedGeneratorVersion property
  • Updated eng/packages/http-client-csharp/package.json dependency version
  • Ran npm install to update package-lock.json
  • Ran eng/packages/http-client-csharp/eng/scripts/Generate.ps1 to regenerate test projects
  • Generated emitter-package.json artifacts using tsp-client
  • Regenerated SDK libraries using the unbranded emitter via dotnet msbuild /t:GenerateCode

This is an automated PR created by the TypeSpec publish pipeline.

Copilot AI review requested due to automatic review settings February 18, 2026 22:42
@github-actions github-actions bot added Client This issue is related to a non-management package CodeGen Issues that relate to code generation labels Feb 18, 2026
Copy link
Contributor

Copilot AI left a 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 updates the repo’s pinned unbranded TypeSpec C# emitter version to 1.0.0-alpha.20260218.5 (and refreshes the corresponding temporary emitter package artifacts) so generation flows use the newer published emitter.

Changes:

  • Bump UnbrandedGeneratorVersion in central props to 1.0.0-alpha.20260218.5.
  • Update @typespec/http-client-csharp dependency version used by eng/packages/http-client-csharp.
  • Refresh eng/http-client-csharp-emitter-package.json and its lockfile to align with the new emitter’s peer dependency set.

Reviewed changes

Copilot reviewed 3 out of 4 changed files in this pull request and generated no comments.

File Description
eng/packages/http-client-csharp/package.json Updates unbranded emitter dependency version used by the local TypeSpec C# package.
eng/http-client-csharp-emitter-package.json Updates the temp emitter package to reference the new unbranded emitter and newer TypeSpec toolchain deps.
eng/http-client-csharp-emitter-package-lock.json Updates the corresponding lockfile to match the updated temp emitter package deps.
eng/Packages.Data.props Updates the UnbrandedGeneratorVersion property to the new alpha version.
Files not reviewed (1)
  • eng/http-client-csharp-emitter-package-lock.json: Language not supported
Comments suppressed due to low confidence (1)

eng/packages/http-client-csharp/package.json:45

  • package.json updates @typespec/http-client-csharp to 1.0.0-alpha.20260218.5, but the local package-lock.json in this folder is still pinned to 1.0.0-alpha.20260213.16 and the devDependencies remain on the older TypeSpec/Azure Tools versions. This will produce a non-reproducible install (and likely peer dependency conflicts) and contradicts the PR description that npm install was run. Please bump the relevant devDependencies to satisfy the new emitter’s peer deps (e.g., TypeSpec 1.9.x / rest+streams+versioning 0.79.x, and Azure Tools 0.65.x, plus any newly required peers like @typespec/sse) and regenerate eng/packages/http-client-csharp/package-lock.json accordingly.
    "@typespec/http-client-csharp": "1.0.0-alpha.20260218.5"
  },
  "devDependencies": {
    "@azure-tools/azure-http-specs": "0.1.0-alpha.35",
    "@azure-tools/typespec-autorest": "0.64.0",

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Client This issue is related to a non-management package CodeGen Issues that relate to code generation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments