Skip to content

Backmerge/release/february 2026 2026 02 26#3983

Merged
tadelesh merged 9 commits intomainfrom
backmerge/release/february-2026-2026-02-26
Feb 27, 2026
Merged

Backmerge/release/february 2026 2026 02 26#3983
tadelesh merged 9 commits intomainfrom
backmerge/release/february-2026-2026-02-26

Conversation

@tadelesh
Copy link
Member

No description provided.

Copilot AI and others added 8 commits February 12, 2026 05:46
…Code (#3929)

- [x] Change `InitializedByFlags.Default` back from `-1` to `0` (no
user-specific initialization setting for sub clients)
- [x] Rename `InitializedByFlags.None` to
`InitializedByFlags.CustomizeCode` (value `4` / `1 << 2` for bitmap
compatibility)
- [x] Update documentation for `Default` to clarify it only works for
sub clients
- [x] Add documentation for `Individually` (1) and `Parent` (2) values
- [x] Move `customizeCode` to end of `InitializedBy` enum in
`decorators.tsp`
- [x] Update `InitializedBy.none` to `InitializedBy.customizeCode` with
value `4` in `decorators.tsp`
- [x] Update decorator validation to accept `4` as valid value
- [x] Validate that `customizeCode` cannot be combined with other values
in a union
- [x] Update all references in source code, tests, CHANGELOG, and
changeset
- [x] Regenerate reference docs via `pnpm run regen-docs`
- [x] Build and test (all 1177 tests pass)
- [x] Format code with `pnpm -w format`
- [x] Code review and security checks passed

<!-- START COPILOT ORIGINAL PROMPT -->



<details>

<summary>Original prompt</summary>

> 
> ----
> 
> *This section details on the original issue you should resolve*
> 
> <issue_title>[Bug]: InitializedByFlags.Default changed to -1
introduced significant codegen changes</issue_title>
> <issue_description>### Describe the bug
> 
> #3877 changed
`InitializedByFlags.Default` to `-1` which means all the bits are set.
As a result, when emitters don't explicitly test for this value, clients
are treated as having the `Parent` and `Individually` bits set, so we
emit client constructors in addition to client accessors. Before this
change, no client constructors were being emitted.
> 
> To further confuse the issue, the docs for the `Default` flag state
it's `internal only` which makes me think that tcgc should not be
exposing this to callers.
> 
> ### Reproduction
> 
> tcgc `v0.65.0` rebuild any Spector test that has hierarchical clients.
> 
> ### Checklist
> 
> - [x] Follow our [Code of
Conduct](https://github.com/azure/typespec-azure/blob/main/CODE_OF_CONDUCT.md)
> - [x] Check that this issue is about the Azure libraries for typespec.
For bug in the typespec language or core libraries file it in the
[TypeSpec repo](https://github.com/Microsoft/TypeSpec/issues/new/choose)
> - [x] Check that there isn't already an issue that request the same
bug to avoid creating a duplicate.
> - [x] The provided reproduction is a [minimal reproducible
example](https://stackoverflow.com/help/minimal-reproducible-example) of
the bug.</issue_description>
> 
> <agent_instructions>Change back default value to 0 and not doc it to
be internal only. The default is used by some languages that tells that
there is no user specific initialization setting. Rename `None` to
`CustomizeCode` that means the initialization needs to be handled
manually. Make sure doc could represent the usage and use `pnpm -w
format` and `pnpm -w change add` to format code and add
changeset.</agent_instructions>
> 
> ## Comments on the Issue (you are @copilot in this section)
> 
> <comments>
> </comments>
> 


</details>



<!-- START COPILOT CODING AGENT SUFFIX -->

- Fixes #3927

<!-- START COPILOT CODING AGENT TIPS -->
---

💡 You can make Copilot smarter by setting up custom instructions,
customizing its development environment and configuring Model Context
Protocol (MCP) servers. Learn more [Copilot coding agent
tips](https://gh.io/copilot-coding-agent-tips) in the docs.

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: tadelesh <1726438+tadelesh@users.noreply.github.com>
Co-authored-by: tadelesh <chenjieshi@microsoft.com>
…emplates (#3945)

Cherry pick of #3941 onto
release branch in preparation for hotfix

Co-authored-by: Copilot <198982749+Copilot@users.noreply.github.com>
Co-authored-by: JoshLove-msft <54595583+JoshLove-msft@users.noreply.github.com>
Co-authored-by: joheredi <21109913+joheredi@users.noreply.github.com>
Co-authored-by: Jose Manuel Heredia Hidalgo <joheredi@microsoft.com>
The fix in #3849 was not
complete.

Cherry-picking
87a540c
@microsoft-github-policy-service microsoft-github-policy-service bot added the lib:tcgc Issues for @azure-tools/typespec-client-generator-core library label Feb 27, 2026
@tadelesh tadelesh enabled auto-merge February 27, 2026 05:39
@pkg-pr-new
Copy link

pkg-pr-new bot commented Feb 27, 2026

Open in StackBlitz

npm i https://pkg.pr.new/@azure-tools/typespec-client-generator-core@3983

commit: 57f0fbe

@azure-sdk
Copy link
Collaborator

❌ There is undocummented changes. Run chronus add to add a changeset or click here.

The following packages have changes but are not documented.

  • @azure-tools/typespec-client-generator-core
Show changes

@azure-sdk
Copy link
Collaborator

You can try these changes here

🛝 Playground 🌐 Website

@tadelesh tadelesh added this pull request to the merge queue Feb 27, 2026
Merged via the queue into main with commit f1f5fd8 Feb 27, 2026
28 checks passed
@tadelesh tadelesh deleted the backmerge/release/february-2026-2026-02-26 branch February 27, 2026 07:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

lib:tcgc Issues for @azure-tools/typespec-client-generator-core library

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants