Bump @azure-tools/typespec-client-generator-core from 0.68.0 to 0.68.2 in /packages/typespec-rust in the typespec group across 1 directory#969
Merged
jhendrixMSFT merged 3 commits intoMay 28, 2026
Conversation
dependabot
Bot
added
dependencies
dependabot
Bot
requested review from
RickWinter,
antkmsft,
heaths and
jhendrixMSFT
as code owners
dependabot
Bot
added
dependencies
Member
|
@dependabot rebase |
Contributor
Author
|
Dependabot can't parse your pnpm-lock.yaml. Because of this, Dependabot cannot update this pull request. |
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/packages/typespec-rust/typespec-63ef11cb3c
branch
from
c3ba405 to
5337aec
Compare
Member
|
There's a codegen change due to unstable sort ordering. This is fixed in #974 |
Bumps the typespec group with 1 update in the /packages/typespec-rust directory: [@azure-tools/typespec-client-generator-core](https://github.com/Azure/typespec-azure). Updates `@azure-tools/typespec-client-generator-core` from 0.68.0 to 0.68.2 - [Release notes](https://github.com/Azure/typespec-azure/releases) - [Commits](https://github.com/Azure/typespec-azure/compare/typespec-azure@0.68.0...@azure-tools/typespec-client-generator-core@0.68.2) --- updated-dependencies: - dependency-name: "@azure-tools/typespec-client-generator-core" dependency-version: 0.68.2 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: typespec ... Signed-off-by: dependabot[bot] <support@github.com>
jhendrixMSFT
force-pushed
the
dependabot/npm_and_yarn/packages/typespec-rust/typespec-63ef11cb3c
branch
from
5337aec to
b921f6b
Compare
tadelesh
pushed a commit
to Azure/typespec-azure
that referenced
this pull request
May 28, 2026
…s model variants (#4508) ## Problem PR #4440 rewrote `listOrphanTypes` to iterate via `listScopedDecoratorData(context, usageKey)`, which follows **decorator application order**. The old code walked namespaces and iterated **models first, then enums, then unions**. This ordering matters because anonymous types (e.g. anonymous model variants inside unions) get their generated name from whichever context processes them first. When `@@usage` on a union appears before `@@usage` on a model that references it, the anonymous variant gets named from the union context (e.g. `RecursiveNullableType1`) instead of the model property context (e.g. `OuterWithNullableValue`). Reported via Azure/typespec-rust#969 — upgrading from TCGC 0.68.0 to 0.68.2 renamed `OuterWithNullableValue` → `RecursiveNullableType1`. ## Fix Collect orphan types into three separate buckets (models, enums, unions) and concatenate them at the end: `[...models, ...enums, ...unions]`. This restores the models-first ordering while preserving the #4440 improvement of discovering types from imported libraries. ## Testing Added a regression test that reproduces the exact scenario from the typespec-rust spec. Co-authored-by: iscai-msft <isabellavcai@gmail.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
jhendrixMSFT
approved these changes
May 28, 2026
heaths
approved these changes
May 28, 2026
jhendrixMSFT
deleted the
dependabot/npm_and_yarn/packages/typespec-rust/typespec-63ef11cb3c
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps the typespec group with 1 update in the /packages/typespec-rust directory: @azure-tools/typespec-client-generator-core.
Updates
@azure-tools/typespec-client-generator-corefrom 0.68.0 to 0.68.2Release notes
Sourced from @azure-tools/typespec-client-generator-core's releases.
Commits
7181847feat: add spector coverage upload for typespec-python (#4483)ccb7d9eBump core from5d83d06to429d74a(#4475)0f6faddupdate versioning of http-client-python (#4482)cb2e2c9Improve benchmark dashboard UI (#4427)0ecab62Bump core from3311b24to5d83d06(#4467)d29a254Backmerge release/may-2026 (tcgc@0.68.1 hotfix) (#4472)86cdf59[Automated][azure-resource-manager] Fix doc comment typos and add suppress do...598b155Bump github/gh-aw from 0.73.0 to 0.74.4 in the actions group (#4437)213d2b2Bump core from431b269to3311b24(#4436)a1b1173Add 0.68 tcgc newsletter (#4439)