docs: add commit rules and branch/PR workflow to copilot instructions by iscai-msft · Pull Request #3 · iscai-msft/typespec

iscai-msft · 2026-07-22T16:04:31Z

Adds two small sections to the repo-root .github/copilot-instructions.md to codify workflow conventions for contributors using Copilot:

Commit instructions -- explicitly calls out pnpm format before committing and advises against committing pnpm-lock.yaml unless necessary.
Branch and PR Workflow (new section) -- documents that branches should be based off Microsoft/typespec main (not a personal fork), and PRs should target that same upstream main branch.

All existing content is preserved; these are purely additive changes.

…@error (microsoft#10555) Using `@defaultResponse` on a model that already has `@statusCode` or `@error` produces duplicate `$ref` entries in OpenAPI output (e.g., `anyOf` with two identical refs). Rather than silently generating invalid output, emit a diagnostic warning at the source. ### Changes - **`packages/openapi/src/lib.ts`** — New `default-response-with-status-code` diagnostic with `statusCode` and `error` message variants - **`packages/openapi/src/decorators.ts`** — `$defaultResponse` now checks the target model for existing `@statusCode` properties and `@error` decoration before setting the wildcard status code - **`packages/openapi/test/decorators.test.ts`** — Tests for both warning cases and the clean no-warning path ### Example ```typespec // This now emits a warning: @error @defaultResponse model DefaultError is Error<500>; // Recommended alternatives: @error model MyError { message: string; } op read(): Data | MyError; // Or split concerns: @error model Error500 is Error<500>; @error @defaultResponse model DefaultError { message: string; } alias Result<T> = T | Error500 | DefaultError; ``` --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: timotheeguerin <1031227+timotheeguerin@users.noreply.github.com> Co-authored-by: Timothee Guerin <tiguerin@microsoft.com>

…icrosoft#10856) TypeSpec linter docs explain how to define rules but did not provide guidance for naming rule IDs beyond examples, which made non-`no-*` rules less predictable. This PR adds concise naming conventions next to `createRule({ name })` so authors can choose consistent, user-readable rule names. - **Added rule naming guidance in linter authoring docs** - Updated `website/src/content/docs/docs/extending-typespec/linters.md` with a new **“Naming convention”** section. - Documented: - short `kebab-case` names - excluding package/library prefix from `name` - `no-<thing>` for prohibitions - `use-<preferred-thing>` for preferred patterns - subject-oriented forms for domain checks (e.g. `<subject>-missing-<thing>`, `<subject>-invalid-<condition>`) - **Clarified user-facing context for rule IDs** - Explicitly notes rule names are surfaced in diagnostics, `tspconfig.yaml`, docs URLs, and suppression comments, guiding authors toward concise readable IDs. ```ts export const rule = createRule({ name: "use-standard-resource-model", // ... }); ``` --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: timotheeguerin <1031227+timotheeguerin@users.noreply.github.com>

The `internal` access modifier has been stable with no issues, so it no longer needs the experimental warning. This removes the `experimental-feature` diagnostic emitted on every use of `internal` and cleans up all associated suppressions. ## Changes - **`modifiers.ts`** — Remove the block that emitted `experimental-feature` (`messageId: "internal"`) whenever the `internal` modifier was used - **`messages.ts`** — Remove the `internal` messageId from the `experimental-feature` diagnostic definition - **`prototypes.tsp`** — Remove `#suppress "experimental-feature"` from `internal extern dec` (decorator declarations were never independently experimental; the suppress was only needed for `internal`) - **`visibility.tsp`, `private.decorators.tsp`** — Retain existing `#suppress "experimental-feature"` on `internal extern fn` declarations — function declarations (`fn`) remain experimental - **`internal.test.ts`** — Update tests to reflect `internal` no longer emits any diagnostic; previously-allowed usages that only expected `experimental-feature` now expect clean compilation - **`access-modifiers.md`** — Remove the "Suppressing the experimental warning" section ### Before / After ```typespec // Before: emits experimental-feature warning, requires suppression #suppress "experimental-feature" "suppress internal warning" internal model MyInternalModel {} // After: no warning, no suppression needed internal model MyInternalModel {} ``` --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: timotheeguerin <1031227+timotheeguerin@users.noreply.github.com>

Co-authored-by: Qiaoqiao Zhang <55688292+qiaozha@users.noreply.github.com>

## Summary - add project-only `features` support in `tspconfig.yaml` with validation for known compiler feature names - gate internal modifier and function declaration experimental warnings behind compiler feature flags for project code - add `tsp info features` to list available compiler features and enabled state ## Validation - `pnpm --filter @typespec/compiler test` - `pnpm --filter @typespec/compiler build` - `pnpm --filter @typespec/compiler lint` - touched-file `prettier --check` - `pnpm chronus verify`

Closes microsoft#10767 This keeps the OpenAPI extension-key validation tied to the metadata object literal, so invalid keys such as `custom` are reported on the offending property instead of the tag name. Verification: - `npx pnpm --filter @typespec/openapi build` - `npx pnpm --filter @typespec/openapi test -- decorators.test.ts` Signed-off-by: kiwigitops <kiwisclubco@gmail.com>

…vscode (microsoft#10847) # Improve telemetry instrumentation and error diagnostics ## Summary Based on analysis of 2 weeks of telemetry data (71K+ events, 2,327 unique users), this PR improves telemetry instrumentation gaps and error diagnostics across the typespec-vscode extension and the compiler LSP server. ## Changes ### Extension telemetry improvements (`packages/typespec-vscode`) **`install-tsp-compiler.ts`** — Added `lastStep` tracking and `logOperationDetailTelemetry` for failure/timeout cases. Previously, all 3 install failures in the dataset had `lastStep=undefined` and zero error detail. **`openapi3-preview.ts`** — Refactored `getOpenApi3OutputFilePath` to return `Result<string>` instead of `string | undefined` to properly distinguish compile failures from user cancellations. Added `lastStep` for the success path (`"Preview panel opened"`). Added compile error details to telemetry. **`extension.ts` (start-server)** — Added `lastStep` for the "compiler not found" state before the install prompt, and for the cancelled-install path. These covered 66 events (34 fail + 32 cancelled) that previously had `lastStep=undefined`. **`extension.ts` (server-path-changed)** — Added `lastStep` for the config change handler. All 30 events previously had `lastStep=undefined`. ### Better error message for node/tsp not on PATH (`packages/typespec-vscode`) **`tsp-executable-resolver.ts`** — When the compiler is found locally but neither `node` nor `tsp` is available on PATH, the extension now shows an actionable error message explaining the likely cause (nvm/fnm/volta PATH not inherited) and three concrete fixes. Previously, this silently fell through to `spawn tsp ENOENT`. This was the #1 root cause of blocked users — 107 failure events from users who never recovered. ### Server-side error detail preservation (`packages/compiler`) **`serverlib.ts`** — Added `wrapUnhandledError` wrapper around all LSP server handlers. When a handler crashes, the wrapper catches the error and re-throws with the full server-side stack trace in the error message (via `inspect(e)`). Previously, the JSON-RPC layer only forwarded `error.message` to the client, so the server-side crash location was completely lost in telemetry. This addresses the 297 `Cannot read properties of undefined (reading 'kind')` errors that were previously opaque. ## Telemetry data highlights - **2,327 total users** in the 2-week window - **101 users (4.3%) completely blocked** — never had a successful `start-server` in 2 weeks - **#1 root cause**: `spawn tsp ENOENT` (node not on PATH) — 107 events from never-recovered users, disproportionately macOS (60%) - **#2 root cause**: compiler not found — 50 events - **297 `reading 'kind'` unhandled errors** — now will include server-side stack for future diagnosis --------- Co-authored-by: Timothee Guerin <timothee.guerin@outlook.com>

…osoft#10455) - [x] Identify root cause in `packages/playground/src/react/standalone.tsx` where `emitter` was being explicitly cleared when a `sampleName` was set - [x] Remove `emitter: undefined` from the save logic so the emitter query param is retained alongside `?sample=...` - [x] Add changelog entry under `.chronus/changes` - [x] Apply prettier formatting --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: JoshLove-msft <54595583+JoshLove-msft@users.noreply.github.com> Co-authored-by: Timothee Guerin <tiguerin@microsoft.com>

…d-server (microsoft#10718) The playground's C# `/generate` endpoint spawns a fresh `dotnet` subprocess on every request, with no caching anywhere in the pipeline. Identical replays (undo/redo, share-link reloads, demo specs hit by many users) pay the full cost. This implements Item 3, Tier 1 of the perf plan: a container-local in-memory response cache. ### Changes - **`playground-server/GenerationCache.cs` (new)** — `IGenerationCache` + `MemoryGenerationCache` backed by `IMemoryCache`. `ComputeKey(generatorName, codeModel, configuration, generatorVersion)` returns a SHA-256 hex over a length-prefixed concatenation (avoids cross-boundary collisions like `"Foo"+"Bar"` vs `"FooBar"+""`). Entry `Size` = body byte length; backing cache `SizeLimit = 256 MB`. Entries are bounded by `SizeLimit`-driven compaction only — there is no TTL, since a new generator binary deploy implicitly invalidates the cache via the version-keyed entries. - **`playground-server/Program.cs`** — registers `AddMemoryCache` + `IGenerationCache` singleton. Reads the generator DLL's `FileVersionInfo.FileVersion` once at startup and folds it into the key, so a deploy of a new binary implicitly invalidates every entry. `/generate` short-circuits on hit (returns cached bytes, skips the subprocess) and serializes-once-then-caches on miss. Responses carry `X-Cache: HIT|MISS`. Cache hits are recorded in telemetry: a hit emits the `PlaygroundGenerate` event with outcome `cache_hit`, and every request carries a `cacheStatus` (`hit`|`miss`) property through the existing telemetry pipeline. - **`playground-server.Tests/` (new NUnit project, 14 tests)** — key determinism & format; sensitivity to each of the four components (including version → invalidation); length-prefix unambiguity; null-argument guards; get/miss/set/overwrite round-trip; `SizeLimit` compaction. ### Cache flow ```csharp var cacheKey = MemoryGenerationCache.ComputeKey(generatorName, body.CodeModel!, body.Configuration!, generatorVersion); if (cache.TryGet(cacheKey, out var cached) && cached is not null) { request.HttpContext.Response.Headers["X-Cache"] = "HIT"; telemetryProperties["cacheStatus"] = "hit"; TrackGenerateEvent("cache_hit"); return Results.Bytes(cached.Body, cached.ContentType); // skips dotnet subprocess } request.HttpContext.Response.Headers["X-Cache"] = "MISS"; telemetryProperties["cacheStatus"] = "miss"; // ...run generator, then: var responseBytes = JsonSerializer.SerializeToUtf8Bytes(new GenerateResponse(files), GenerateJsonContext.Default.GenerateResponse); cache.Set(cacheKey, new CachedGenerationResponse(responseBytes, "application/json")); return Results.Bytes(responseBytes, "application/json"); ``` ### Out of scope Tier 2 file-based cache and Items 1/2/4/5 of the issue. Generator internals are untouched; production `tsp` codegen is unaffected. --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: jorgerangel-msft <102122018+jorgerangel-msft@users.noreply.github.com> Co-authored-by: JoshLove-msft <54595583+JoshLove-msft@users.noreply.github.com> Co-authored-by: jolov <jolov@microsoft.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Co-authored-by: iscai-msft <isabellavcai@gmail.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

…internal (microsoft#10852) A convenience method generated as `public` but taking a parameter whose type is `internal` (e.g. a model customized to internal via `client.tsp` or custom code) fails to compile with an inconsistent-accessibility error. ## Changes - **`ScmMethodProviderCollection`**: added `GetConvenienceMethodModifiers`, which downgrades a convenience method from `public` to `internal` when the enclosing type is not internal and not private (covering public, protected, and similar visibilities) and any signature parameter type is non-public (`!p.Type.IsPublic`). Applied only to the generator-controlled signature path; customized partial-method signatures keep the user's explicit modifiers, and already-internal/private enclosing types are left untouched. - **Tests**: added coverage for the internal-parameter case via a `client.tsp` access override (method becomes `internal`), the internal-parameter case via custom code using a TestData `internal partial class` (method becomes `internal`), and the public-parameter case (method stays `public`). ```csharp private MethodSignatureModifiers GetConvenienceMethodModifiers( MethodSignatureModifiers modifiers, IReadOnlyList<ParameterProvider> signatureParameters) { var enclosingTypeModifiers = EnclosingType.DeclarationModifiers; if (modifiers.HasFlag(MethodSignatureModifiers.Public) && !enclosingTypeModifiers.HasFlag(TypeSignatureModifiers.Internal) && !enclosingTypeModifiers.HasFlag(TypeSignatureModifiers.Private) && signatureParameters.Any(p => !p.Type.IsPublic)) { modifiers &= ~MethodSignatureModifiers.Public; modifiers |= MethodSignatureModifiers.Internal; } return modifiers; } ``` Regenerating the existing test libraries produced no output diffs, confirming the change only affects the previously-broken internal-parameter scenario. --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: jorgerangel-msft <102122018+jorgerangel-msft@users.noreply.github.com>

…on in Build-Packages.ps1" (microsoft#10881) Reverts microsoft#10817 After discussion, we revert this PR to avoid duplicated alpha release for same python emitter content.

…ttp-client-python (microsoft#10864) Bumps [fast-xml-parser](https://github.com/NaturalIntelligence/fast-xml-parser) from 5.5.10 to 5.8.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/NaturalIntelligence/fast-xml-parser/releases">fast-xml-parser's releases</a>.</em></p> <blockquote> <h2>update strnum, FXB. Use xml-naming for DOCTYPE</h2> <ul> <li>integrate xml-naming to validate DOCTYPE entity name and notation name (using qname because of backward compatibility) <ul> <li>This will consider xml-version as well. '1.0' is default</li> </ul> </li> <li>update strnum to 2.3.0 <ul> <li>You can set octal and binary parsing which is by deault off</li> </ul> </li> <li>update fast-xml-builder to 1.2.0 <ul> <li>can sanitize tag names if found invalid</li> <li>fix format output</li> </ul> </li> </ul> <h2>fix minor old bugs and update builder</h2> <ul> <li>fix: alwaysCreateTextNode should create text node when attributes are present for self closing node</li> <li>fix stop node expression when ns prefix is removed (found by <a href="https://github.com/iruizsalinas">iruizsalinas</a>)</li> <li>update XML Builder to 1.1.7</li> <li>mark addEntity deprecated</li> </ul> <h2>backward compatibility for numerical external entity, fix <a href="https://redirect.github.com/NaturalIntelligence/fast-xml-parser/issues/705">#705</a>, <a href="https://redirect.github.com/NaturalIntelligence/fast-xml-parser/issues/817">#817</a></h2> <ul> <li>allow numerical external entity for backward compatibility</li> <li>fix <a href="https://redirect.github.com/NaturalIntelligence/fast-xml-parser/issues/705">#705</a>: attributesGroupName working with preserveOrder</li> <li>fix <a href="https://redirect.github.com/NaturalIntelligence/fast-xml-parser/issues/817">#817</a>: stackoverflow when tag expression is very long</li> </ul> <h2>upgrade <code>@nodable/entities</code> and FXB</h2> <ul> <li>Use <code>@nodable/entities</code> v2.1.0 <ul> <li>breaking changes <ul> <li>single entity scan. You're not allowed to use entity value to form another entity name.</li> <li>you cant add numeric external entity</li> <li>entity error message when expantion limit is crossed might change</li> </ul> </li> <li>typings are updated for new options related to process entity</li> <li>please follow documentation of <code>@nodable/entities</code> for more detail.</li> <li>performance <ul> <li>if processEntities is false, then there should not be impact on performance.</li> <li>if processEntities is true, but you dont pass entity decoder separately then performance may degrade by approx 8-10%</li> <li>if processEntities is true, and you pass entity decoder separately <ul> <li>if no entity then performance should be same as before</li> <li>if there are entities then performance should be increased from past versions</li> </ul> </li> </ul> </li> <li>ignoreAttributes is not required to be set to set xml version for NCR entity value</li> </ul> </li> <li>update 'fast-xml-builder' to sanitize malicious CDATA and comment's content</li> </ul> <h2>use <code>@nodable/entities</code> to replace entities</h2> <ul> <li>No API change</li> <li>No change in performance for basic usage</li> <li>No typing change</li> <li>No config change</li> <li>new dependency</li> <li>breaking: error messages for entities might have been changed.</li> <li></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/NaturalIntelligence/fast-xml-parser/compare/v5.5.12...v5.6.0">https://github.com/NaturalIntelligence/fast-xml-parser/compare/v5.5.12...v5.6.0</a></p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/NaturalIntelligence/fast-xml-parser/blob/master/CHANGELOG.md">fast-xml-parser's changelog</a>.</em></p> <blockquote> <p>Note: If you find missing information about particular minor version, that version must have been changed without any functional change in this library.</p> <p>Note: Due to some last quick changes on v4, detail of v4.5.3 & v4.5.4 are not updated here. v4.5.4x is the last tag of v4 in github repository. I'm extremely sorry for the confusion</p> <p>*<em>5.8.0 / 2026-05-12</em></p> <ul> <li>integrate xml-naming to validate DOCTYPE entity name and notation name (using qname becaue of backward compatibility) <ul> <li>This will consider xml-version as well. '1.0' is default</li> </ul> </li> <li>update strnum to 2.3.0 <ul> <li>You can set octal and binary parsing which is bydeault off</li> </ul> </li> <li>update fast-xml-builder to 1.2.0 <ul> <li>can sanitize tag names if found invalid</li> <li>fix format output</li> </ul> </li> </ul> <p><strong>5.7.3 / 2006-05-05</strong></p> <ul> <li>fix: alwaysCreateTextNode should create text node when attributes are present for self closing node</li> <li>fix stop node expression when ns prefix is removed (found by <a href="https://github.com/iruizsalinas">iruizsalinas</a>)</li> <li>update XML Builder to 1.1.7</li> <li>mark addEntity deprecated</li> </ul> <p><strong>5.7.2 / 2026-04-25</strong></p> <ul> <li>allow numerical external entity for backward compatibility</li> <li>fix <a href="https://redirect.github.com/NaturalIntelligence/fast-xml-parser/issues/705">#705</a>: attributesGroupName working with preserveOrder</li> <li>fix <a href="https://redirect.github.com/NaturalIntelligence/fast-xml-parser/issues/817">#817</a>: stackoverflow when tag expression is very long</li> </ul> <p><strong>5.7.1 / 2026-04-20</strong></p> <ul> <li>fix typo in CJS typing file</li> </ul> <p><strong>5.7.0 / 2026-04-17</strong></p> <ul> <li>Use <code>@nodable/entities</code> v2.1.0 <ul> <li>breaking changes <ul> <li>single entity scan. You're not allowed to user entity value to form another entity name.</li> <li>you cant add numeric external entity</li> <li>entity error message when expantion limit is crossed might change</li> </ul> </li> <li>typings are updated for new options related to process entity</li> <li>please follow documentation of <code>@nodable/entities</code> for more detail.</li> <li>performance <ul> <li>if processEntities is false, then there should not be impact on performance.</li> <li>if processEntities is true, but you dont pass entity decoder separately then performance may degrade by approx 8-10%</li> <li>if processEntities is true, and you pass entity decoder separately <ul> <li>if no entity then performance should be same as before</li> <li>if there are entities then performance should be increased from past versions</li> </ul> </li> </ul> </li> <li>ignoreAttributes is not required to be set to set xml version for NCR entity value</li> </ul> </li> <li>update 'fast-xml-builder' to sanitize malicious CDATA and comment's content</li> </ul> <p><strong>5.6.0 / 2026-04-15</strong></p> <ul> <li>fix: entity replacement for numeric entities</li> <li>use <code>@nodable/entities</code> to replace entities <ul> <li>this may change some error messages related to entities expansion limit or inavlid use</li> <li>post check would be exposed in future version</li> </ul> </li> </ul>  </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/NaturalIntelligence/fast-xml-parser/commit/4bcee44a034ec99706b68b16e31f4072505b13e9"><code>4bcee44</code></a> for release</li> <li><a href="https://github.com/NaturalIntelligence/fast-xml-parser/commit/8a287bf2524f0a3a4c32be7edaedced3a9839ab8"><code>8a287bf</code></a> release info</li> <li><a href="https://github.com/NaturalIntelligence/fast-xml-parser/commit/50b01dcacb8fe21f986a9e7b55800bd96401fe58"><code>50b01dc</code></a> Use "<code>@byspec/xml</code>" for testing</li> <li><a href="https://github.com/NaturalIntelligence/fast-xml-parser/commit/816b652c83249edc1569c523f7bc3e13b3ef929c"><code>816b652</code></a> update typings to mark validator use deprecated</li> <li><a href="https://github.com/NaturalIntelligence/fast-xml-parser/commit/8ad0e650bcdb05001b533f27bc01f2e873d87cc5"><code>8ad0e65</code></a> update fast-xml-builder and strnum</li> <li><a href="https://github.com/NaturalIntelligence/fast-xml-parser/commit/58e967ed7f8208e4896b607cf5a057a5659f97c6"><code>58e967e</code></a> integrate xml-naming</li> <li><a href="https://github.com/NaturalIntelligence/fast-xml-parser/commit/42fa3c3af8e0d59e9fe213785a1b204b39338d2b"><code>42fa3c3</code></a> separate XML validator, UPDATE DOCS</li> <li><a href="https://github.com/NaturalIntelligence/fast-xml-parser/commit/d6d80429b1d1f1420902e1cebac6fe7831ba0839"><code>d6d8042</code></a> update to release</li> <li><a href="https://github.com/NaturalIntelligence/fast-xml-parser/commit/d2633709699520c514208ea70e31adb6d71ab0e8"><code>d263370</code></a> remove dev dependency 'he'</li> <li><a href="https://github.com/NaturalIntelligence/fast-xml-parser/commit/f9c9a2c19f819ab6fe0856ef4e94d6aa28fe1eec"><code>f9c9a2c</code></a> update builder to 1.1.7</li> <li>Additional commits viewable in <a href="https://github.com/NaturalIntelligence/fast-xml-parser/compare/v5.5.10...v5.8.0">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=fast-xml-parser&package-manager=npm_and_yarn&previous-version=5.5.10&new-version=5.8.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/microsoft/typespec/network/alerts). </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

This updates stale PR triage timing so inactive PRs are marked stale after 14 days instead of 30. It also updates the post-stale grace period to 14 days, resulting in a 28-day total inactivity window before automatic closure. - **Policy timing update** - Changed initial stale trigger in `.github/policies/pr.stale.yml` from `noActivitySince: 30` to `noActivitySince: 14`. - Updated the first scheduled search description to reflect the 14-day threshold. - Changed stale-close trigger from `noActivitySince: 30` to `noActivitySince: 14` for already-stale PRs. - **Lifecycle messaging alignment** - Updated stale notification copy to say closure happens after **14 additional days** once marked stale. - Updated close notification and description text from 60/44 days to 28 days total inactivity. ```yaml # before - description: Ping user when the PR has not been updated in 30 days filters: - noActivitySince: days: 30 # after - description: Ping user when the PR has not been updated in 14 days filters: - noActivitySince: days: 14 ``` --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: timotheeguerin <1031227+timotheeguerin@users.noreply.github.com>

Bumps the ui group with 2 updates: [react-dom](https://github.com/facebook/react/tree/HEAD/packages/react-dom) and [react](https://github.com/facebook/react/tree/HEAD/packages/react). Updates `react-dom` from 19.2.6 to 19.2.7 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/facebook/react/releases">react-dom's releases</a>.</em></p> <blockquote> <h2>19.2.7 (June 1st, 2026)</h2> <h2>React Server Components</h2> <ul> <li>Fixed missing <code>FormData</code> entries in Server Actions which regressed in 19.2.6 (<a href="https://redirect.github.com/facebook/react/pull/36566">#36566</a> by <a href="https://github.com/unstubbable"><code>@unstubbable</code></a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/facebook/react/commit/6117d7cca4906492c51fe6a03381e35adfd86e7d"><code>6117d7c</code></a> Version 19.2.7 (<a href="https://github.com/facebook/react/tree/HEAD/packages/react-dom/issues/36591">#36591</a>)</li> <li>See full diff in <a href="https://github.com/facebook/react/commits/v19.2.7/packages/react-dom">compare view</a></li> </ul> </details> <details> <summary>Maintainer changes</summary> <p>This version was pushed to npm by <a href="https://www.npmjs.com/~GitHub%20Actions">GitHub Actions</a>, a new releaser for react-dom since your current version.</p> </details> <br /> Updates `react` from 17.0.2 to 19.2.7 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/facebook/react/releases">react's releases</a>.</em></p> <blockquote> <h2>19.2.7 (June 1st, 2026)</h2> <h2>React Server Components</h2> <ul> <li>Fixed missing <code>FormData</code> entries in Server Actions which regressed in 19.2.6 (<a href="https://redirect.github.com/facebook/react/pull/36566">#36566</a> by <a href="https://github.com/unstubbable"><code>@unstubbable</code></a>)</li> </ul> <h2>19.2.6 (May 6th, 2026)</h2> <h2>React Server Components</h2> <ul> <li>Type hardening and performance improvements (<a href="https://redirect.github.com/facebook/react/pull/36425">#36425</a> by <a href="https://github.com/eps1lon"><code>@eps1lon</code></a> and <a href="https://github.com/unstubbable"><code>@unstubbable</code></a>)</li> </ul> <h2>19.2.5 (April 8th, 2026)</h2> <h2>React Server Components</h2> <ul> <li>Add more cycle protections (<a href="https://redirect.github.com/facebook/react/pull/36236">#36236</a> by <a href="https://github.com/eps1lon"><code>@eps1lon</code></a> and <a href="https://github.com/unstubbable"><code>@unstubbable</code></a>)</li> </ul> <h2>19.2.4 (January 26th, 2026)</h2> <h2>React Server Components</h2> <ul> <li>Add more DoS mitigations to Server Actions, and harden Server Components (<a href="https://redirect.github.com/facebook/react/pull/35632">#35632</a> by <a href="https://github.com/gnoff"><code>@gnoff</code></a>, <a href="https://github.com/lubieowoce"><code>@lubieowoce</code></a>, <a href="https://github.com/sebmarkbage"><code>@sebmarkbage</code></a>, <a href="https://github.com/unstubbable"><code>@unstubbable</code></a>)</li> </ul> <h2>19.2.3 (December 11th, 2025)</h2> <h2>React Server Components</h2> <ul> <li>Add extra loop protection to React Server Functions (<a href="https://github.com/sebmarkbage"><code>@sebmarkbage</code></a> <a href="https://redirect.github.com/facebook/react/pull/35351">#35351</a>)</li> </ul> <h2>19.2.2 (December 11th, 2025)</h2> <h2>React Server Components</h2> <ul> <li>Move <code>react-server-dom-webpack/*.unbundled</code> to private <code>react-server-dom-unbundled</code> (<a href="https://github.com/eps1lon"><code>@eps1lon</code></a> <a href="https://redirect.github.com/facebook/react/pull/35290">facebook/react#35290</a>)</li> <li>Patch Promise cycles and toString on Server Functions (<a href="https://github.com/sebmarkbage"><code>@sebmarkbage</code></a>, <a href="https://github.com/unstubbable"><code>@unstubbable</code></a> <a href="https://redirect.github.com/facebook/react/pull/35289">#35289</a>, <a href="https://redirect.github.com/facebook/react/pull/35345">#35345</a>)</li> </ul> <h2>19.2.1 (December 3rd, 2025)</h2> <h2>React Server Components</h2> <ul> <li>Bring React Server Component fixes to Server Actions (<a href="https://github.com/sebmarkbage"><code>@sebmarkbage</code></a> <a href="https://redirect.github.com/facebook/react/pull/35277">#35277</a>)</li> </ul> <h2>19.2.0 (Oct 1, 2025)</h2> <p>Below is a list of all new features, APIs, and bug fixes.</p> <p>Read the <a href="https://react.dev/blog/2025/10/01/react-19-2">React 19.2 release post</a> for more information.</p> <h2>New React Features</h2> <ul> <li><a href="https://react.dev/reference/react/Activity"><code><Activity></code></a>: A new API to hide and restore the UI and internal state of its children.</li> <li><a href="https://react.dev/reference/react/useEffectEvent"><code>useEffectEvent</code></a> is a React Hook that lets you extract non-reactive logic into an <a href="https://react.dev/learn/separating-events-from-effects#declaring-an-effect-event">Effect Event</a>.</li> <li><a href="https://react.dev/reference/react/cacheSignal"><code>cacheSignal</code></a> (for RSCs) lets your know when the <code>cache()</code> lifetime is over.</li> <li><a href="https://react.dev/reference/developer-tooling/react-performance-tracks">React Performance tracks</a> appear on the Performance panel’s timeline in your browser developer tools</li> </ul> <h2>New React DOM Features</h2>  </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/facebook/react/blob/main/CHANGELOG.md">react's changelog</a>.</em></p> <blockquote> <h2>19.2.1 (Dec 3, 2025)</h2> <h3>React Server Components</h3> <ul> <li>Bring React Server Component fixes to Server Actions (<a href="https://github.com/sebmarkbage"><code>@sebmarkbage</code></a> <a href="https://redirect.github.com/facebook/react/pull/35277">#35277</a>)</li> </ul> <h2>19.2.0 (October 1st, 2025)</h2> <p>Below is a list of all new features, APIs, and bug fixes.</p> <p>Read the <a href="https://react.dev/blog/2025/10/01/react-19-2">React 19.2 release post</a> for more information.</p> <h3>New React Features</h3> <ul> <li><a href="https://react.dev/reference/react/Activity"><code><Activity></code></a>: A new API to hide and restore the UI and internal state of its children.</li> <li><a href="https://react.dev/reference/react/useEffectEvent"><code>useEffectEvent</code></a> is a React Hook that lets you extract non-reactive logic into an <a href="https://react.dev/learn/separating-events-from-effects#declaring-an-effect-event">Effect Event</a>.</li> <li><a href="https://react.dev/reference/react/cacheSignal"><code>cacheSignal</code></a> (for RSCs) lets your know when the <code>cache()</code> lifetime is over.</li> <li><a href="https://react.dev/reference/dev-tools/react-performance-tracks">React Performance tracks</a> appear on the Performance panel’s timeline in your browser developer tools</li> </ul> <h3>New React DOM Features</h3> <ul> <li>Added resume APIs for partial pre-rendering with Web Streams: <ul> <li><a href="https://react.dev/reference/react-dom/server/resume"><code>resume</code></a>: to resume a prerender to a stream.</li> <li><a href="https://react.dev/reference/react-dom/static/resumeAndPrerender"><code>resumeAndPrerender</code></a>: to resume a prerender to HTML.</li> </ul> </li> <li>Added resume APIs for partial pre-rendering with Node Streams: <ul> <li><a href="https://react.dev/reference/react-dom/server/resumeToPipeableStream"><code>resumeToPipeableStream</code></a>: to resume a prerender to a stream.</li> <li><a href="https://react.dev/reference/react-dom/static/resumeAndPrerenderToNodeStream"><code>resumeAndPrerenderToNodeStream</code></a>: to resume a prerender to HTML.</li> </ul> </li> <li>Updated <a href="https://react.dev/reference/react-dom/static/prerender"><code>prerender</code></a> APIs to return a <code>postponed</code> state that can be passed to the <code>resume</code> APIs.</li> </ul> <h3>Notable changes</h3> <ul> <li>React DOM now batches suspense boundary reveals, matching the behavior of client side rendering. This change is especially noticeable when animating the reveal of Suspense boundaries e.g. with the upcoming <code><ViewTransition></code> Component. React will batch as much reveals as possible before the first paint while trying to hit popular first-contentful paint metrics.</li> <li>Add Node Web Streams (<code>prerender</code>, <code>renderToReadableStream</code>) to server-side-rendering APIs for Node.js</li> <li>Use underscore instead of <code>:</code> IDs generated by useId</li> </ul> <h3>All Changes</h3> <h4>React</h4> <ul> <li><code><Activity /></code> was developed over many years, starting before <code>ClassComponent.setState</code> (<a href="https://github.com/acdlite"><code>@acdlite</code></a> <a href="https://github.com/sebmarkbage"><code>@sebmarkbage</code></a> and many others)</li> <li>Stringify context as "SomeContext" instead of "SomeContext.Provider" (<a href="https://github.com/kassens"><code>@kassens</code></a> <a href="https://redirect.github.com/facebook/react/pull/33507">#33507</a>)</li> <li>Include stack of cause of React instrumentation errors with <code>%o</code> placeholder (<a href="https://github.com/eps1lon"><code>@eps1lon</code></a> <a href="https://redirect.github.com/facebook/react/pull/34198">#34198</a>)</li> <li>Fix infinite <code>useDeferredValue</code> loop in popstate event (<a href="https://github.com/acdlite"><code>@acdlite</code></a> <a href="https://redirect.github.com/facebook/react/pull/32821">#32821</a>)</li> <li>Fix a bug when an initial value was passed to <code>useDeferredValue</code> (<a href="https://github.com/acdlite"><code>@acdlite</code></a> <a href="https://redirect.github.com/facebook/react/pull/34376">#34376</a>)</li> <li>Fix a crash when submitting forms with Client Actions (<a href="https://github.com/sebmarkbage"><code>@sebmarkbage</code></a> <a href="https://redirect.github.com/facebook/react/pull/33055">#33055</a>)</li> <li>Hide/unhide the content of dehydrated suspense boundaries if they resuspend (<a href="https://github.com/sebmarkbage"><code>@sebmarkbage</code></a> <a href="https://redirect.github.com/facebook/react/pull/32900">#32900</a>)</li> <li>Avoid stack overflow on wide trees during Hot Reload (<a href="https://github.com/sophiebits"><code>@sophiebits</code></a> <a href="https://redirect.github.com/facebook/react/pull/34145">#34145</a>)</li> <li>Improve Owner and Component stacks in various places (<a href="https://github.com/sebmarkbage"><code>@sebmarkbage</code></a>, <a href="https://github.com/eps1lon"><code>@eps1lon</code></a>: <a href="https://redirect.github.com/facebook/react/pull/33629">#33629</a>, <a href="https://redirect.github.com/facebook/react/pull/33724">#33724</a>, <a href="https://redirect.github.com/facebook/react/pull/32735">#32735</a>, <a href="https://redirect.github.com/facebook/react/pull/33723">#33723</a>)</li> <li>Add <code>cacheSignal</code> (<a href="https://github.com/sebmarkbage"><code>@sebmarkbage</code></a> <a href="https://redirect.github.com/facebook/react/pull/33557">#33557</a>)</li> </ul>  </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/facebook/react/commit/6117d7cca4906492c51fe6a03381e35adfd86e7d"><code>6117d7c</code></a> Version 19.2.7 (<a href="https://github.com/facebook/react/tree/HEAD/packages/react/issues/36591">#36591</a>)</li> <li><a href="https://github.com/facebook/react/commit/eaf3e95ca92be7a23d3c9cc8ffd6f199a40be401"><code>eaf3e95</code></a> Version 19.2.6</li> <li><a href="https://github.com/facebook/react/commit/23f4f9f30da9e9af2108c18bb197bae75ab584ea"><code>23f4f9f</code></a> 19.2.5</li> <li><a href="https://github.com/facebook/react/commit/90ab3f89f4824ac763b6f877c6f711200d1338d2"><code>90ab3f8</code></a> Version 19.2.4</li> <li><a href="https://github.com/facebook/react/commit/612e371fb215498edde4c853bd1e0c8e9203808f"><code>612e371</code></a> Version 19.2.3</li> <li><a href="https://github.com/facebook/react/commit/b910fc15e38d4fa80003819ddb7a928a3c3dca5d"><code>b910fc1</code></a> Version 19.2.2</li> <li><a href="https://github.com/facebook/react/commit/053df4e8561ef4caecef31c330f4178ac25e255b"><code>053df4e</code></a> Version 19.2.1</li> <li><a href="https://github.com/facebook/react/commit/5667a41fe4d81aa806f6c1e8814b17975e33b317"><code>5667a41</code></a> Bump next prerelease version numbers (<a href="https://github.com/facebook/react/tree/HEAD/packages/react/issues/34639">#34639</a>)</li> <li><a href="https://github.com/facebook/react/commit/8bb7241f4c773376893701bfe8b8ff03687342a0"><code>8bb7241</code></a> Bump useEffectEvent to Canary (<a href="https://github.com/facebook/react/tree/HEAD/packages/react/issues/34610">#34610</a>)</li> <li><a href="https://github.com/facebook/react/commit/e3c9656d20618ed321aea85cb3d844cbd1dce078"><code>e3c9656</code></a> Ensure Performance Track are Clamped and Don't overlap (<a href="https://github.com/facebook/react/tree/HEAD/packages/react/issues/34509">#34509</a>)</li> <li>Additional commits viewable in <a href="https://github.com/facebook/react/commits/v19.2.7/packages/react">compare view</a></li> </ul> </details> <details> <summary>Maintainer changes</summary> <p>This version was pushed to npm by <a href="https://www.npmjs.com/~GitHub%20Actions">GitHub Actions</a>, a new releaser for react since your current version.</p> </details> <br /> Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore <dependency name> major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore <dependency name> minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore <dependency name>` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore <dependency name>` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore <dependency name> <ignore condition>` will remove the ignore condition of the specified dependency and ignore conditions </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

…nd discriminator without subtypes (microsoft#10841) Add two new cross-language Spector test scenarios identified from Go and TypeScript emitter bug fixes: ## 1. Dollar-sign prefixed query parameters (`parameters/query/DollarSign`) Tests that emitters correctly handle `$`-prefixed query parameter names on the wire (e.g. `$filter`, `$top`, `$skip`, `$orderby`). Common in OData-style APIs. - Identified from: Azure/autorest.go#1922 ## 2. Discriminated type without subtypes (`type/model/inheritance/single-discriminator`) Tests a `@discriminator`-decorated model with no extending subtypes. Emitters should still generate the polymorphic type infrastructure. - Identified from: Azure/autorest.go#1892 Both scenarios include `main.tsp` definitions, `mockapi.ts` implementations, and updated `spec-summary.md`. --------- Co-authored-by: iscai-msft <isabellavcai@gmail.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

…ft#10869) ## Summary Refactors `playground.tsx` by extracting scattered state management into focused, testable hooks. ### Changes | New File | Responsibility | |----------|---------------| | `compilation/compile.ts` | Pure async compile/findOutputFiles/emptyOutputDir | | `hooks/use-compilation.ts` | Compile queuing, stale output preservation, markers | | `hooks/use-monaco-sync.ts` | Bidirectional Monaco ↔ state sync | | `hooks/use-debounced-compile.ts` | Debounced recompile subscription | | `hooks/use-editor-actions.ts` | Save, format, file-bug, keybindings | ### Result - `playground.tsx`: ~600 → ~360 lines (40% reduction) - No public API changes (fully backward-compatible) - All tests pass, lint clean

Co-authored-by: iscai-msft <isabellavcai@gmail.com>

- Functions were previously not correctly validating that arguments assigned to the rest parameter constraint were compatible with the constraint. This fixes that issue and adds a regression test. - Function diagnostics were incorrectly targeted in some cases that this change addresses. - Function type signatures in `tspd` were rendered a little bit incorrectly and this PR addresses that. - Function documentation had a few typos that this PR fixes (TypeScript -> TypeSpec, one invalid identifier in an example) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

…t#10640)

- [x] Update `MAX_PYTHON_VERSION` from `"3.13"` to `"3.14"` in `packages/http-client-python/generator/pygen/codegen/serializers/general_serializer.py` so emitted `pyproject.toml` includes the Python 3.14 classifier - [x] Add changelog entry for `@typespec/http-client-python` (feature kind) --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: johanste <15110018+johanste@users.noreply.github.com> Co-authored-by: iscai-msft <isabellavcai@gmail.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

@deprecated

Replace the custom deepClone utility and JSON.parse(JSON.stringify(...)) patterns with structuredClone. ## Changes - Replaced all internal deepClone() calls with structuredClone() - Replaced JSON.parse(JSON.stringify(...)) deep copy patterns with structuredClone() - Deprecated the public deepClone export with @deprecated JSDoc tag (kept for backward compat) - Cleaned up unused imports Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

…entSettings when BindCore is customized (microsoft#10905) When a generated `ClientSettings` type's `BindCore(IConfigurationSection)` is moved to custom code, the generated partial still references `IConfigurationSection` in its XML doc summary, but `using Microsoft.Extensions.Configuration;` was dropped — so the generated code no longer compiles. **Root cause:** Namespace imports are registered from actual type references during writing. The class description used a plain string `<see cref="IConfigurationSection"/>` rather than a real type reference, so it never registered the namespace. The only thing registering `Microsoft.Extensions.Configuration` was the generated `BindCore` parameter type — once `BindCore` is customized away and filtered out, nothing registers it. ### Changes - **`ClientSettingsProvider.BuildDescription`**: reference the actual types via the `:C` cref formatter (matching the `ClientOptionsProvider` convention) instead of hardcoded `<see cref>` strings. This registers the `Microsoft.Extensions.Configuration` namespace while rendering an identical cref, so normal generated output is unchanged. ```csharp // before => $"Represents the settings used to configure a <see cref=\"{_clientProvider.Name}\"/> that can be loaded from an <see cref=\"IConfigurationSection\"/>."; // after => $"Represents the settings used to configure a {_clientProvider.Type:C} that can be loaded from an {IConfigurationSectionType:C}."; ``` - **Regression test** (`TestGeneratedSettings_WithCustomizedBindCore`) + TestData: uses TestData to move `BindCore` into a custom partial, asserts it is no longer generated, and validates the full generated output against an expected snapshot file (`TestData/ClientSettingsProviderTests/TestGeneratedSettings_WithCustomizedBindCore.cs`), confirming the `using` is still emitted. Fails without the fix. --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: jorgerangel-msft <102122018+jorgerangel-msft@users.noreply.github.com>

…ed` directive (microsoft#10901) PR microsoft#4453 added `deprecated` import support for models and properties but missed operations. An OpenAPI operation with `deprecated: true` would be silently dropped during conversion. ## Changes - **`transform-paths.ts`**: Extract `operation.deprecated` as a `TypeSpecDirective` and attach it to the resulting `TypeSpecOperation` (including through `splitOperationByContentType`). - **`generate-operation.ts`**: Add `generateDirectives` emission; refactor line-joining so directives render on their own line (preamble: doc + directives `\n`-joined; body: tags + decorators + `op` space-joined) — `#deprecated` inline with decorators is invalid TypeSpec syntax. ## Example ```yaml # Input paths: /widgets: get: operationId: Widgets_list deprecated: true responses: ... ``` ```tsp // Before (deprecated silently dropped) op Widgets_list(): ...; // After #deprecated "deprecated" op Widgets_list(): ...; ``` --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: baywet <7905502+baywet@users.noreply.github.com>

@OverRide

…ster (microsoft#10897) ## Summary `ApplyCodeFixExpect.toEqual` now accepts `Record<string, string>` to assert on multiple files after a code fix is applied. This enables testing code fixes that write to a different file (e.g., adding augment decorators to a `client.tsp`). ## Changes - Overloaded `toEqual` to accept `string | Record<string, string>` - Single-file (`string`): existing behavior unchanged - Multi-file (`Record<string, string>`): captures all `writeFile` calls, asserts only on specified files (partial match) - Supports code fixes that create new files not in the original input ## Example ```ts await ruleTester .expect({ "main.tsp": `import "./client.tsp";\nmodel Foo { name: string; }`, "client.tsp": ``, }) .applyCodeFix("add-client-override") .toEqual({ "client.tsp": `@@OverRide(Foo.name, "clientName");\n`, }); ```

…11295) ## Summary Node has shipped native source-map support for stack traces since v14.6 via `process.setSourceMapsEnabled(true)`, and every workspace package now requires Node `>=22`. The third-party `source-map-support` dependency is therefore no longer needed. This replaces the `source-map-support/register.js` import with the native API in the CLI entrypoints and drops the dependency. ## Changes - Replace `source-map-support/register.js` with `process.setSourceMapsEnabled(true)` in the CLI entrypoints (removing the associated `try/catch` + `@ts-ignore`/eslint-disable): - `packages/compiler/src/core/cli/cli.ts` - `packages/pack/src/cli.ts` - `packages/tspd/src/cli.ts` - `packages/bundler/src/cli.ts` - `packages/spector/src/cli/cli.ts` - Remove `source-map-support` from the `pnpm-workspace.yaml` catalog and from the `package.json` of `@typespec/compiler`, `@typespec/pack`, `@typespec/tspd`, and `@typespec/spector`. - Refresh `pnpm-lock.yaml`. ## Out of scope `packages/http-client-*/package-lock.json` reference `source-map-support` only transitively via the **published** `@typespec/spector`; those npm-managed lockfiles regenerate separately when spector is republished. ## Validation - All affected packages build. - Lint (oxlint) and format (prettier) clean on touched files. - Remaining `pnpm-lock.yaml` hits are legitimate transitive deps (`@babel/register`, chronus tooling), not a direct dependency.

…ests (microsoft#11298) ## Summary - add C# Spector coverage for exploded model query parameters - add C# Spector coverage for lossy integer duration encodings - regenerate the affected routes and duration clients ## Validation - `Test-Spector.ps1 -filter http/routes` (18 passed, 9 skipped) - `Test-Spector.ps1 -filter http/encode/duration` (58 passed) - `npm run build` - `npm run cop` Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

## Summary - add an `InternalHelperProvider` base that registers itself with `AddTypeToKeep(..., isRoot: false)` - default helper declarations to `internal static`, with direct modifier overrides for non-static helpers - preserve generic non-root helpers during post-processing and regenerate the local sample ## Validation - `npm run build` - `npm test` - `npm run cop` - focused helper retention tests - formatting completed; emitter lint is currently blocked by the repository's missing ESLint 10 flat config --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

) ## Summary The `parameters.query.QueryTests#testDollarSign` test in `http-client-generator-clientcore-test` was disabled pending the `@typespec/http-specs` dollar-sign route fix. That fix is now published (http-specs `0.1.0-alpha.38`), and the already-generated `SpecialCharClient.dollarSign` code matches the current spec (route `/parameters/query/special-char/dollar-sign`, `@QueryParam("$filter")`). This PR removes the `@Disabled` annotation (and its now-unused import) to enable the test. ## Validation `mvn test -Dtest=parameters.query.QueryTests` against the spector mock server: **2 run, 0 failures, 0 skipped**. --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

…icrosoft#11221) Fixes microsoft#11141 Auto-generate a reference documentation page per **linter rule** and per **diagnostic** with `tspd`, so these pages stop being hand-written and drift-prone. > [!NOTE] > This PR is scoped to the `tspd` documentation generation. The `referenceDocs.baseUrl` url auto-generation and the language server hover that surfaces these docs at a reported error are split into a follow-up PR. ## Compiler - **`docs` field on diagnostics and linter rules.** Both `createRule` and diagnostic definitions accept a `docs` field for extended documentation: ```ts export const myRule = createRule({ name: "my-rule", severity: "warning", description: "Short description.", docs: fileRef.fromPackageRoot("src/rules/my-rule.md"), messages: { /* ... */ }, }); ``` The value is `string | FileRef`: either inline markdown, or a `FileRef` created via `fileRef.fromPackageRoot("...")`. A `FileRef` is a plain `{ kind, path }` data object read **lazily** by tooling, so it is safe to include in code bundled for the browser (e.g. the playground). Because the docs live on the definition, they are available at compile time, not just to `tspd`. ## tspd `tspd doc` now renders: - one page per rule -> `reference/rules/<name>.md` - one page per diagnostic -> `reference/diagnostics/<code>.md` (each shows its severity) - a `documentation-missing` warning for every rule/diagnostic without `docs`. ## Pilots Content is faithfully migrated from the hand-written pages, which are then deleted: - **`@typespec/http`** — the `op-reference-container-route` rule. - **`@typespec/openapi3`** — 6 diagnostics (`path-query`, `duplicate-header`, `inline-cycle`, `invalid-schema`, `invalid-server-variable`, `union-null`); the old hand-written `emitters/openapi3/diagnostics.md` is replaced by the generated pages under `reference/diagnostics/`. ## Validation - Built `compiler`, `tspd`, `http`, `openapi3`; regen is stable (running it twice produces no diff). - `lint` green for the touched packages; the `op-reference-container-route` rule tests pass. --------- Co-authored-by: tadelesh <chenjieshi@microsoft.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

) The OpenAPI `License` object supports an `identifier` field (SPDX expression) since spec v3.1, but TypeSpec's `@info` decorator was missing it — causing a spurious "unknown prop" warning. ## Changes ### `@typespec/openapi` - Added `identifier?: string` to the `License` model and TypeScript interfaces - Added `license-url-identifier-conflict` diagnostic: `url` and `identifier` are mutually exclusive (per spec); both being set is now a compile-time error - Validation enforced in the `$info` decorator ### `@typespec/openapi3` — Emitter - **OpenAPI 3.1 / 3.2**: `identifier` emits as the native `identifier` field - **OpenAPI 3.0**: `identifier` is emitted as the `x-oai-license-identifier` extension ### `@typespec/openapi3` — Converter (OpenAPI → TypeSpec) - `identifier` in 3.1 documents maps directly to `identifier` - `x-oai-license-identifier` in 3.0 documents is promoted to `identifier` ## Example ```typespec @info(#{ license: #{ name: "MIT", identifier: "MIT" }, }) namespace MyService; ``` Emits for OpenAPI 3.1: ```json "license": { "name": "MIT", "identifier": "MIT" } ``` Emits for OpenAPI 3.0: ```json "license": { "name": "MIT", "x-oai-license-identifier": "MIT" } ``` closes microsoft#11302 --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: baywet <7905502+baywet@users.noreply.github.com> Co-authored-by: Vincent Biret <vibiret@microsoft.com> Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

…11297) This updates dependency resolution to enforce `sigstore@4.1.1`, addressing vulnerability exposure from earlier transitive versions. The lockfile is refreshed so installs consistently resolve to the pinned version. - **Dependency resolution hardening** - Added a workspace-level pnpm override for `sigstore` in `pnpm-workspace.yaml`. - Ensures all transitive resolution paths converge on `4.1.1`. - **Deterministic install output** - Regenerated `pnpm-lock.yaml` to apply the override in resolved package graph. - Removed prior lockfile resolution paths that pulled older `sigstore` versions. ```yaml # pnpm-workspace.yaml overrides: sigstore: 4.1.1 ``` --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: timotheeguerin <1031227+timotheeguerin@users.noreply.github.com> Co-authored-by: Timothee Guerin <tiguerin@microsoft.com> Co-authored-by: Mike Harder <mharder@microsoft.com>

fixes microsoft#6870 --------- Co-authored-by: iscai-msft <isabellavcai@gmail.com> Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

…microsoft#11303) Extracts the self-contained `tsp init` template-loading refactor out of microsoft#11299 into its own PR. ## What Replaces `getExecutionRoot()`-based template resolution in `tsp init` with a first-class `TemplateSource` abstraction, with three implementations behind one interface: - **`FileSystemTemplateSource`** — the default (installed/`node`) path; reads `templates/` from the compiler package root. No `getExecutionRoot()` dependency. - **`InMemoryTemplateSource`** — serves the index and every template file from an in-memory map (used by the standalone single-executable to serve templates offline). - **`RemoteTemplateSource`** — `--templates-url`; keeps the untrusted-source confirmation and relative-file resolution. ## Why Template loading previously went through the `CompilerHost` filesystem contract anchored at `getExecutionRoot()`, which also serves the stdlib. Serving templates from an embedded/offline source required masquerading an in-memory map as a real filesystem and overloading `getExecutionRoot()`. This refactor decouples template resolution from the host FS contract so each context supplies its own source, and leaves `getExecutionRoot()` solely for the stdlib. ## Notes - No behavior change on the normal path: `init` defaults to `FileSystemTemplateSource`. - Language server (`getTypeSpecCoreTemplates` / `scaffoldNewProject`) and the VS Code extension keep working; the extension threads a `TemplateSource` through `create-tsp-project`. - Backward-compatible: `serverlib.ts` / `server/types.ts` are unchanged. - This is the first of a split of microsoft#11299; the standalone single-executable feature remains in microsoft#11299 and builds on top of this.

…osoft#11312) ## Summary Removes the unused `backupPath` fallback argument from the internal `runScript` helper (`packages/compiler/src/runner.ts`) and its two callers. `runScript(relativePath, backupPath)` used to fall back to `backupPath` when `relativePath` did not exist under the resolved package root. Both call sites (`cmd/tsp.js`, `cmd/tsp-server.js`) always pass a `relativePath` that exists, so the fallback (and its `checkFileExists` helper + `access` import) is dead code. This is a pure, self-contained cleanup extracted out of microsoft#11299 (standalone SEA rewrite) so that PR stays focused on the feature. The standalone CLI does not use `runScript`. ## History / why it is safe to remove The `backupPath` fallback was added in microsoft#1410 and shipped in `@cadl-lang/compiler` **0.38.2** (Dec 2022) as a patch: _"Revert breaking change to global cli usage."_ That PR introduced the stable indirection entrypoints `entrypoints/cli.js` and `entrypoints/server.js`. Before 0.38.2 the global CLI booted the compiler directly at `dist/core/cli/cli.js` (and `dist/server/server.js`). Because a **globally-installed** CLI resolves and runs the **locally-installed** compiler, a global 0.38.2 CLI could hit an older local compiler that did not yet have the `entrypoints/` files. The `backupPath` (`dist/core/cli/cli.js` / `dist/server/server.js`) was the fallback so the global CLI could still boot those pre-0.38.2 local installs. Every supported compiler version has shipped `entrypoints/cli.js` / `entrypoints/server.js` since 0.38.2, so the fallback branch is now unreachable dead code. ## Changes - `runner.ts`: `runScript(relativePath)` — dropped `backupPath` param, `checkFileExists`, and the now-unused `access` import. - `cmd/tsp.js` / `cmd/tsp-server.js`: drop the second argument. ## Validation - `tsc -p packages/compiler/tsconfig.build.json` passes.

…ation (microsoft#11316) ## Summary Adds a `--rules-dir` option (and matching `rulesDir` API option) to `tspd doc` to control the directory where the per-rule reference pages are written. Since the tspd change that auto-generates one reference page per linter rule, those pages are always emitted under `<output-dir>/rules/`. Some consumers (e.g. `typespec-azure`) generate their reference docs into a `reference/` output dir but want the rule pages to keep their historical location one level up (`libraries/<lib>/rules/<name>`), so that existing rule URLs stay stable. This adds a small, backwards-compatible knob to control that location. ## Details - New CLI flag `--rules-dir <dir>` on `tspd doc`. - New `rulesDir` option on `GenerateLibraryDocsOptions` and `RenderToStarlightMarkdownOptions`. - Defaults to `"rules"` (relative to `--output-dir`) — **no change** to existing behavior. - Can be set to a path that escapes the output dir (e.g. `"../rules"`) to place rule pages outside the generated reference folder. - The `StarlightRenderer.linterRuleLink` (used by `linter.md`) honors the configured dir so cross-links resolve correctly. ## Example ```bash # default (unchanged): pages at <output-dir>/rules/<name>.md tspd doc . --enable-experimental --output-dir ./reference # keep rule pages outside the reference folder: <output-dir>/../rules/<name>.md tspd doc . --enable-experimental --output-dir ./reference --rules-dir ../rules ```

…pat (microsoft#11315) The underscore back-compat pass restores previously-shipped underscore names (e.g. `Tls1_0`) when the current spec normalizes them (e.g. `Tls10`). For extensible enums whose custom code re-adds the underscore member, the restoration renamed the *generated* member back to the underscore form — colliding with the custom member and removing the generated symbol it referenced. Example custom code that broke: ```csharp public partial struct ServiceBusMinimumTlsVersion { // references the generated `Tls10`; back-compat renamed it to `Tls1_0`, // producing a duplicate and dropping `Tls10` public static ServiceBusMinimumTlsVersion Tls1_0 { get; } = Tls10; } ``` ## Changes - **`EnumProvider.GetBackCompatibleName`**: new optional `customMemberNames` argument; skips the underscore restoration when the restored name already exists in custom code, keeping the generated name. - **`ExtensibleEnumProvider.BuildEnumValues`**: collects custom member names from `CustomCodeView.Properties` (case-insensitive) and threads them through. Uses `CustomCodeView` rather than `CanonicalView` to avoid the `CanonicalView → Properties → EnumValues → BuildEnumValues` recursion cycle; it contributes the same custom members. - **Tests**: adds `BackCompat_ExtensibleEnumCustomCodeTakesPrecedenceOverPreservedUnderscores` with `(Custom)`/`(Last)` TestData; existing `BackCompat_ExtensibleEnumUnderscoresPreserved` remains as the no-custom-code case. --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: jorgerangel-msft <102122018+jorgerangel-msft@users.noreply.github.com>

…t#11320) ## Problem The tspd change that auto-generates one reference page per linter rule (microsoft#11221) moved the `@typespec/http` linter rule page from its historical location: - **Before:** `https://typespec.io/docs/libraries/http/rules/op-reference-container-route` - **After:** `https://typespec.io/docs/libraries/http/reference/rules/op-reference-container-route` This is a breaking change to the public documentation URL. The rule's own `url` field, external links, and the diagnostic "see documentation" link all still point at the historical `libraries/http/rules/<name>` location, which now 404s. ## Fix Use the `--rules-dir ../rules` option (added in microsoft#11316) in http's `regen-docs` script so the per-rule reference pages are written back to `libraries/http/rules/<name>`, restoring the original URL. - `packages/http/package.json` — add `--rules-dir ../rules` to `regen-docs`. - Regenerated docs: the rule page moves back to `libraries/http/rules/op-reference-container-route.md` (100% rename) and `linter.md` links back to `../rules/...`. - `current-sidebar.ts` — re-enable the http "Rules" sidebar group (`hasLinterRules: true`), which autogenerates from `libraries/http/rules`. `@typespec/http` is the only library in this repo that ships linter rules, so no other library is affected. ## Validation - `regen-docs` is stable (running it twice produces no diff). - The restored page URL `libraries/http/rules/op-reference-container-route` matches the rule's hardcoded `url` again. - `chronus verify` passes. Co-authored-by: tadelesh <chenjieshi@microsoft.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

) ## Summary Adds XML serialization support to the `@typespec/http-client-java` generator (azure-core v1 flavor). When any model is serialized/deserialized as XML, the generator now: 1. **Emits two helper classes** into the implementation package — `XmlSerializer` (an `ObjectSerializer` backed by `azure-xml` + reflective `fromXml(XmlReader)`) and `XmlSerializerProviders` (factory). Emission is gated on `isAzureV1()` and any generating model with `ClientModel::isUsedInXml`. 2. **Uses the XML serializer overload** in generated convenience methods — a static `SERIALIZER` field is declared on sync/async convenience clients, and `BinaryData.fromObject(input, SERIALIZER)` / `toObject(X.class, SERIALIZER)` are emitted when the request/response content type is XML. The azure-v2 / clientcore flavor handles `XmlSerializable` natively and is unaffected. Non-XML output is unchanged. ## Changes - **Generator core**: new resource templates `XmlSerializer.java` / `XmlSerializerProviders.java`; XML-aware `SupportedMimeType` handling in `ConvenienceMethodTemplateBase`, `ConvenienceSyncMethodTemplate`, `ConvenienceAsyncMethodTemplate`; static `SERIALIZER` field in `ServiceSyncClientTemplate` / `ServiceAsyncClientTemplate`; constants in `ClientModelUtil`. - **Generator plugin**: `TypeSpecPlugin.writeHelperClasses` emits the two helper files for XML models. - **Test module**: enabled the `payload/xml` spec, regenerated clients, and ported the XML test suite. ## Testing - `payload.xml.XmlTests`: **26 run, 0 failures, 2 skipped** (namespace scenarios). - Verified end-to-end: generator rebuild → emitter pack → `tsp compile` → generated output adopted into `src` matches, tests green. --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

…t#11289) Follow-up fix to microsoft#11197 (pylint-guidelines-checker `0.5.9` bump). On regeneration, DPG models emitted a **duplicate docstring**: `:keyword:`/`:paramtype:` lines in the class docstring duplicated the existing `:ivar:`/`:vartype:` entries (e.g. `InvalidAuth`). ## Changes - Remove the redundant keyword-doc generation for DPG models (the source of the duplicated lines). - For DPG models, suppress `docstring-keyword-should-match-keyword-only` at the class line instead — DPG `__init__` overloads have empty bodies, so the checker validates keyword-only args against the *class* docstring, and we intentionally document those args once as `:ivar:` entries. ## Validation - locally ran `npm run regenerate` and full regeneration (azure + unbranded) succeeds; docstrings no longer duplicated. ## todo - [ ] disable `no-cross-package-private-import` in pylintrc of `typespec-azure` --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: Yuchao Yan <yuchaoyan@microsoft.com>

…icrosoft#11326) ## Problem Since tspd generates one reference page per linter rule and diagnostic from each definition's `docs` field, the generated pages checked into the website content duplicate their source markdown: - `website/.../libraries/http/rules/op-reference-container-route.md` ↔ `packages/http/src/rules/op-reference-container-route.md` - `website/.../emitters/openapi3/reference/diagnostics/*.md` (6 files) ↔ `packages/openapi3/src/diagnostics/*.md` Keeping both copies in git means every content edit has to be made (or regenerated) in two places. ## Fix Follow the same approach as [Azure/typespec-azure#4968](Azure/typespec-azure#4968) and the repo's existing `js-api` precedent (`**/docs/**/js-api/` is already gitignored): stop tracking the generated pages and regenerate them during the website build. - `.gitignore` — ignore the generated pages: - `website/src/content/docs/docs/**/rules/` - `website/src/content/docs/docs/**/reference/diagnostics/` - Untrack the 7 generated pages (their source markdown under `packages/*/src/**` remains the single tracked copy). The website build regenerates them: `website` build runs `build:web`, which runs `regen-all-packages-docs` before `astro check`/`astro build`. ## Validation - Deleted the generated pages from disk, ran `regen-docs` for http + openapi3, and confirmed all 7 pages are reproduced at the same paths — and git now treats them as ignored (no longer tracked, not shown as untracked). - `@typespec/http` (rules) and `@typespec/openapi3` (diagnostics) are the only libraries in this repo that use the `docs` field, so the globs only match generated content. - `chronus verify` passes (no shipped package changes). Co-authored-by: tadelesh <chenjieshi@microsoft.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

… merged by mistake that way (microsoft#11321) ## Summary - Reverted `pnpm-lock.yaml` to remove registry-proxy-injected `tarball:` URLs (load-balanced `ms-feed-N.pkgs.visualstudio.com` hosts) that are environment-specific and break CI. The lockfile is now integrity-only again. - Added a `check-lockfile` script (`eng/common/scripts/check-lockfile.ts`) that fails if any `tarball:` URL is present in `pnpm-lock.yaml`. - Wired it into the `version-consistency` job in `consistency.yml`. ## Why not a pnpm setting? pnpm's `lockfile-include-tarball-url=false` is already the default and is [known to be flaky](pnpm/pnpm#6667) when the registry host differs from the tarball host, so it does not reliably prevent this. A lightweight CI guard is the robust option. ## Validation - `pnpm run check-lockfile` passes on the cleaned lockfile. - Verified it exits non-zero when a `tarball:` URL is injected. - `tsc -p ./tsconfig.eng.json --noEmit` passes.

Fixes six open **A11y_TypeSpec** website accessibility bugs (all Sev2, `meta:website`) filed against typespec.io. | Issue | WCAG | Fix | | ----- | ---- | --- | | microsoft#10789 | 2.4.1 Bypass Blocks | Added a visible-on-focus **"Skip to main content"** link + a focusable `<main id tabindex="-1">` landmark to the non-docs page layout. | | microsoft#10791 | 2.1.1 Keyboard | Made the OpenAPI page sample **carousel keyboard operable** — converted the `role="tab"` anchors (no `href`) to `<button>`s with the full ARIA tabs pattern. | | microsoft#10793 | 1.3.1 Info & Relationships | Gave the docs **sidebar a distinct landmark name** ("Documentation") via an i18n override so it no longer duplicates the header's "Main" nav. | | microsoft#10794 | 1.4.12 Text Spacing | Kept the header on a **single row** under increased text spacing: hide the version banner in the narrow desktop range (1024–1200px) and let the nav wrap as a fallback instead of overlapping. | | microsoft#10795 | 1.4.10 Reflow | On docs pages the site header menu button overlapped Starlight's sidebar menu button (and the search button). **Hid the redundant site menu button** and reserved space for Starlight's; the site links remain reachable from the Starlight mobile menu. | | microsoft#10796 | 1.4.4 Resize Text | Same root cause as microsoft#10795 — resolved by the same change plus syncing `--sl-nav-height` to the real header height so content offsets track the header. | ## Verification Each fix was verified in a locally running dev server with Playwright/Chromium: - Skip link is the first focusable element and moves focus to `<main>` on activation. - Carousel tabs are focusable buttons; ArrowLeft/Right switch panels and update `aria-selected`. - Docs page exposes distinct `Main` and `Documentation` nav landmarks. - Header stays a single row at all widths, including the tester's ~1918px text-spacing repro. - Only one menu button on docs pages at mobile widths, with no overlap against the search button; the Starlight menu contains the site links so nothing is hidden. `astro check` (0 errors / 0 warnings / 0 hints), `oxlint`, and `prettier` all pass. > `@typespec/website` is a private package (not published), so no changelog entry is required.

…ft#11273) `@typespec/http-specs` was not registered under any Chronus version policy, leaving it unmanaged for versioning purposes. ## Changes - Added `@typespec/http-specs` to the `typespec-preview` lockstep policy in `.chronus/config.yaml` so it versions in lockstep with other preview packages. Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: timotheeguerin <1031227+timotheeguerin@users.noreply.github.com> Co-authored-by: Timothee Guerin <tiguerin@microsoft.com>

## What `eng/emitter-diff` **diffs the generated code produced by two versions of a TypeSpec emitter**. It resolves a *baseline* and a *head* source tree (each a local folder or a GitHub url/sha), runs the emitter's own regenerate command in each, and renders the difference between the generated output as a clickable **HTML report** (default) plus a terminal summary. For go/rust/languages in azure/typespec-azure you would add the language to the registry and update your package.json to reference this in the core submodule (or you can directly call the cli script (no registry needed) with the correct flags set in your package.json) ## How it works - **Refs** (`--baseline` / `--head`): `local:/path`, `github:owner/repo@<sha|branch>`, or `gh:<sha|branch>` (this repo). Head defaults to the current working tree; baseline defaults to `upstream/main` (or `origin/main`). - **Setup**: a tree the tool fetches fresh from GitHub is prepared with the preset's `--setup` (install + build). The current working tree and `local:` paths are assumed already built and never installed by the tool. A commit-keyed cached worktree is prepared once, so reruns skip re-setup. - **Baseline-output cache**: baseline generated output is cached per profile + baseline commit, so iterative local runs only regenerate head. Disabled in CI with `--ci`. On a cache hit the baseline tree is not even checked out — its identity is resolved with a cheap shallow fetch. - **Filtering a subset of tests**: everything after `--` is appended to the regenerate command verbatim on both sides, so you can forward the regenerate script's own filter flags (e.g. python's `--name authentication/api-key --flavor azure`) to diff only part of the suite. ## Flags `--emitter <name>` (preset: `python`, `typescript`/`ts`), `--command`, `--emitter-path`, `--generated-code-path`, `--setup` (repeatable) / `--no-setup`, `--baseline` / `--head`, `--work-dir`, `--sequential` (regenerate sides one at a time instead of in parallel), `--ci`, `--html`, `--fail-on-diff`, and `-- <args>` passthrough. See `eng/emitter-diff/README.md`. ## Changes - **`eng/emitter-diff/`** — the tool: CLI/orchestrator (`cli.ts`), ref resolver for local/github/`gh:` refs with a commit-keyed worktree cache (`resolver.ts`), emitter presets (`registry.ts`), a zero-dependency HTML/terminal diff renderer (`diff.ts`), the local baseline-output cache (`baseline-cache.ts`), shared types/utilities, `tsconfig.json`, and `README.md`. - **`packages/http-client-python/package.json`** — adds the `diff-spector-tests` script (`tsx ../../eng/emitter-diff/src/cli.ts --emitter python`). - **`.github/workflows/ci-emitter-diff-python.yml`** — the PR workflow (below). - **`cspell.yaml`**, **`.chronus/changes/…`** — a spelling allow-list entry and an `internal` changeset. ## CI behavior The `python / emitter diff` workflow runs on PRs that touch `http-client-python` or the tool. It diffs this PR's emitter against the **PR merge-base** (overridable via `workflow_dispatch`), uploads the rendered **HTML report** as an artifact, and posts/updates a **sticky PR comment** with the diff summary. It is **informational**: the job fails only on a tool/build error — **never on a diff**. --------- Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Splitting from the rest of dep upgrade as it creates a lot of diff

…ft#11319) The regen preview pipeline aborted mgmt library regeneration with `Unbranded package not found: .../csharp-debug-.../typespec-http-client-csharp-<version>.tgz`. `Update-MgmtGenerator` resolves the unbranded emitter from the debug folder as `typespec-http-client-csharp-$LocalVersion.tgz`, but `Submit-AzureSdkForNetPr.ps1` referenced the unbranded `.tgz` directly from `$BuildArtifactsPath` and only staged the `.nupkg` files and the locally built Azure `.tgz` into the debug folder — leaving the unbranded package absent from where the mgmt build looks. ### Changes - **`Submit-AzureSdkForNetPr.ps1`**: Copy the unbranded `typespec-http-client-csharp-*.tgz` from build artifacts into `$debugFolder` and point `$unbrandedPackagePath` at that copy, so both the Azure and management plane generators resolve it from the same location. --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: jorgerangel-msft <102122018+jorgerangel-msft@users.noreply.github.com>

## Summary Routine dependency upgrade pass for July 2026. - Bump `pnpm` to `11.10.0`. - Update catalog dependencies: `@astrojs/starlight`, `@babel/*` (7 → 8), `@expressive-code/core` / `astro-expressive-code`, `vite`, `@vscode/test-web`, `oxlint-tsgolint`, `vite-plugin-dts`, etc. - Raise `minimumReleaseAge` to 7 days. ## Note on astro `astro` is **pinned to `7.0.3`** rather than bumped. Versions `7.0.4`-`7.0.6` contain a static-build regression ([withastro/astro#17306](withastro/astro#17306)) where dynamic file-extension endpoints (e.g. `docs/[...slug].md.ts`) with `trailingSlash: "always"` fail the build with `NoMatchingStaticPathFound`. The upstream fix ([#17320](withastro/astro#17320)) ships in `7.0.8`, which is published but still within our 7-day new-package quarantine. The pin should be dropped once `7.0.8` clears quarantine. ## Validation - `website` builds successfully with the pin (1128 pages, no `NoMatchingStaticPathFound`).

…m 2.18.7 to 2.18.9 in /packages/http-client-java/generator/http-client-generator-clientcore-test (microsoft#11334) Bumps [com.fasterxml.jackson.core:jackson-databind](https://github.com/FasterXML/jackson) from 2.18.7 to 2.18.9. <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/FasterXML/jackson/commits">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=com.fasterxml.jackson.core:jackson-databind&package-manager=maven&previous-version=2.18.7&new-version=2.18.9)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/microsoft/typespec/network/alerts). </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

… skip raw bytes payloads (microsoft#11329) ## Fix XML serializer gating for byte[] payloads ### Problem A recent change (support XML serialization in the http-client-java generator) emitted a static XML `ObjectSerializer SERIALIZER` field whenever an operation had an XML content-type. This was wrong in two cases: 1. **Raw `byte[]`/`BinaryData` payloads** (e.g. an operation returning a raw XML document as `bytes`, like `azure-analytics-planetarycomputer`'s `getWmtsCapabilities`). Here the `SERIALIZER` referenced an `XmlSerializerProviders` helper that is only generated for models actually used in XML, so the generated code failed to compile. 2. **Non `azure-v1` data-plane clients.** XML `ObjectSerializer` handling only applies to the `azure-core` (v1) data-plane flavor. ### Fix - Gate `SERIALIZER` emission on `isAzureV1() && isDataPlaneClient()`. - Only use the XML `ObjectSerializer` when the payload is an actual model, i.e. not `byte[]`/`BinaryData`/`Base64Url`. - Inspect the **convenience** method's model body types (unwrapping `Mono`/`Flux`/`Response`/`ResponseBase`/`PagedIterable`/`PagedFlux`/`PagedResponseBase`) instead of the protocol method's `BinaryData` type. ### Verification - New `tsp/xml-bytes-verify.tsp` case (data-plane azure-v1 op returning `bytes` with `application/xml`) generates committed source under `tsptest/xmlbytesverify`. - New reflection-based `XmlBytesVerifyTests` asserts the generated clients declare **no** static `SERIALIZER` field for raw bytes payloads, with a positive control on `payload.xml.SimpleModelValueClient`. - Regenerating `payload/xml` produces identical output (`SERIALIZER` count unchanged at 312), confirming real XML model clients are unaffected. Ref: Azure/azure-sdk-for-java#49877 --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

…soft#11339) Adds a 7-day cooldown to all dependabot update entries so newly published packages must age before Dependabot opens PRs, satisfying the quarantine policy. - **All ecosystems (pip, npm, github-actions)**: added `cooldown: default-days: 7` Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: timotheeguerin <1031227+timotheeguerin@users.noreply.github.com> Co-authored-by: Timothee Guerin <tiguerin@microsoft.com>

- Add explicit pnpm format rule and pnpm-lock.yaml avoidance to Commit instructions - Add new Branch and PR Workflow section with guidance on branching from upstream main and PRing against it Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: d6793634-e102-42e8-b249-6e10ff537a39

github-actions · 2026-07-22T16:08:36Z

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

The following packages have changes but are not documented.

❌@typespec/asset-emitter
❌@typespec/events
❌@typespec/html-program-viewer
❌@typespec/http-canonicalization
❌@typespec/http-client-js
❌@typespec/http-client-python
❌@typespec/http-client
❌@typespec/http-server-csharp
❌@typespec/http-server-js
❌@typespec/internal-build-utils
❌@typespec/json-schema
❌@typespec/library-linter
❌@typespec/mutator-framework
❌@typespec/playground
❌@typespec/prettier-plugin-typespec
❌@typespec/protobuf
❌@typespec/rest
❌@typespec/spec-coverage-sdk
❌@typespec/sse
❌@typespec/streams
❌tmlanguage-generator
❌@typespec/versioning
❌@typespec/xml

The following packages have already been documented:

✅ @typespec/bundler
✅ @typespec/compiler
✅ @typespec/emitter-framework
✅ @typespec/graphql
✅ @typespec/http-client-java
✅ @typespec/http-specs
✅ @typespec/http
✅ @typespec/openapi
✅ @typespec/openapi3
✅ @typespec/spec-api
✅ @typespec/spector
✅ @typespec/tspd

Show changes

`@typespec/http-client-java` - dependencies ✏️

Update http-client-java Node.js dependencies

`@typespec/http-client-java` - internal ✏️

Ignore modifications to META-INF metadata.json files

`@typespec/emitter-framework` - feature ✏️

Add Python Pydantic helpers to the emitter framework: PydanticClassDeclaration, PydanticSettingsClassDeclaration, and PydanticRootModelDeclaration components, along with field_validator, model_validator, field_serializer, and computed_field decorator helpers.

`@typespec/compiler` - feature ✏️

Add setAutoDecorator API to programmatically apply an auto decorator to a target, mirroring what the synthesized auto dec implementation does when the decorator is written in source. This lets emitters and mutators mark synthetic types without reaching into the program state map directly.,> ,> ts,> import { setAutoDecorator } from "@typespec/compiler";,> ,> setAutoDecorator(program, "MyLib.myFlag", target);,>

`@typespec/http-client-java` - internal ✏️

Formatting

`@typespec/http-client-java` - internal ✏️

Add service/multiple-services generation and end-to-end test coverage in http-client-generator-test.

`@typespec/http-client-java` - internal ✏️

Add e2e tests

`@typespec/http-client-java` - internal ✏️

Add SpecialChars e2e test, encode/boolean test (disabled), and type/union/discriminated e2e tests

`@typespec/http-client-java` - dependencies ✏️

Update http-client-java Node.js dependencies and regenerate Java test assets

`@typespec/openapi3` - internal ✏️

Provide extended documentation for several diagnostics (path-query, duplicate-header, inline-cycle, invalid-schema, invalid-server-variable, union-null) via co-located markdown files.

`@typespec/http-client-java` - feature ✏️

Support clientApiVersions

`@typespec/graphql` - internal ✏️

Add @typespec/graphql emitter for generating GraphQL SDL from TypeSpec definitions

`@typespec/http-client-java` - internal ✏️

Reformat augment decorator arguments in test files to match updated formatter style.

`@typespec/http-client-java` - internal ✏️

Reformat a test spec affected by the compiler formatter change keeping is/extends inline for multi-argument template references (whitespace only, no semantic change).

`@typespec/http-client-java` - internal ✏️

Reformat union template arguments in test files to match updated formatter style.

`@typespec/http-client-java` - fix ✏️

Fix null LRO error response body handling in generated management clients.

`@typespec/http` - internal ✏️

Keep the generated linter rule reference pages at their historical libraries/http/rules/<name> location so existing rule documentation URLs stay stable.

`@typespec/http-client-java` - fix ✏️

Fix multi-client packages generating a separate ServiceVersion enum per client when all clients share the same api-versions. The api-version comparison now compares version strings instead of ApiVersion object references, restoring a single shared ServiceVersion for such packages.

`typespec-vscode` - fix ✏️

Fix a shell command injection in the tsp compile task provider. Tasks now run via vscode.ProcessExecution with arguments passed as an array instead of vscode.ShellExecution, so workspace file paths and task arguments are no longer interpreted by the OS shell. The task args is now specified as an array of arguments.

`@typespec/http-client-java` - internal ✏️

Add e2e tests for parameters/body-root, parameters/query special char, type/model/inheritance/single-discriminator no-subtypes, azure/resourcemanager/common-properties arm-resource-identifiers, and azure/resourcemanager/management-group scenarios

`@typespec/http-client-java` - internal ✏️

Enable the parameters.query.QueryTests dollar-sign test in the clientcore test module now that the @typespec/http-specs dollar-sign route fix is published.

`@typespec/http-client-java` - fix ✏️

Fix XML serialization to only apply for azure-v1 data-plane clients, and to skip the XML ObjectSerializer for raw byte[]/BinaryData payloads that are not structured XML models. This avoids emitting a reference to a non-generated XmlSerializerProviders helper (which caused a build break) for operations that return raw XML bytes.

`@typespec/http-client-java` - dependencies ✏️

Bump Node.js dependencies for http-client-java and align dependency ranges in test package overrides.

`@typespec/http-client-java` - internal ✏️

Replace js-yaml with yaml for code-model serialization and drop lodash in favor of a built-in array comparison.

`@typespec/http-client-java` - dependencies ✏️

Update Node.js dependencies to latest (compiler 1.13.0, TCGC 0.69.0, azure-core 0.69.0) and bump version to 0.9.0

`@typespec/http-client-java` - dependencies ✏️

Update Node.js dependencies

`@typespec/http-client-java` - dependencies ✏️

Update Node.js dependencies

`@typespec/http-client-java` - fix ✏️

Overload async client method was not generated for advanced-versioning.

`@typespec/http-client-java` - feature ✏️

Support XML serialization for models: generate XmlSerializer helper classes and use the XML ObjectSerializer overload of toObject/fromObject in convenience methods for XML request/response bodies.

`@typespec/http-client-java` - fix ✏️

Do not throw on a per-service api-version map; treat it as undefined so a client with a single api-version can still be generated.

`@typespec/http-client-java` - fix ✏️

Fix duplicate method in generated samples, when advanced-versioning=true

`@typespec/http-client-java` - dependencies ✏️

Update Node.js dependencies: @azure-tools/typespec-autorest 0.69.1, @azure-tools/typespec-azure-resource-manager 0.69.1, @azure-tools/typespec-azure-rulesets 0.69.1, @microsoft/api-extractor 7.58.9, @types/node 25.9.3, @vitest/coverage-v8 4.1.9, @vitest/ui 4.1.9, vitest 4.1.9

`@typespec/http-client-java` - fix ✏️

Follow-up on exact name feature, after TCGC bug fix.

`@typespec/http-client-java` - fix ✏️

fix bug that nullable not handled correctly

`@typespec/http-client-java` - feature ✏️

Support advanced-versioning for mixed api-version client

`@typespec/http-client-java` - feature ✏️

Support crossLanguageVersion

`@typespec/http-client-java` - feature ✏️

Support exact name from TCGC.

`@typespec/compiler` - internal ✏️

Refactor tsp init template loading around a URI-based TemplateSource abstraction. A UriTemplateSource handles local and remote templates (paths and URLs), while built-in ("core") templates are addressed through an internal: scheme that resolves to an injectable provider. This lets alternative hosts (e.g. an offline single-executable compiler) serve bundled templates via an InMemoryTemplateSource without coupling template loading to the CompilerHost filesystem.

`@typespec/openapi` - feature ✏️

Add identifier field to the License model in @typespec/openapi. This is an SPDX license expression for the API (e.g. "MIT", "Apache-2.0"). The identifier and url fields are mutually exclusive. For OpenAPI 3.1+, identifier is emitted as-is; for OpenAPI 3.0, it is emitted as the x-oai-license-identifier extension. Importing an OpenAPI document also supports reading back identifier (or x-oai-license-identifier for 3.0 documents).,> ,> typespec,> @info(#{,> license: #{ name: "MIT", identifier: "MIT" },,> }),> namespace MyService;,>

`@typespec/openapi3` - feature ✏️

Add identifier field to the License model in @typespec/openapi. This is an SPDX license expression for the API (e.g. "MIT", "Apache-2.0"). The identifier and url fields are mutually exclusive. For OpenAPI 3.1+, identifier is emitted as-is; for OpenAPI 3.0, it is emitted as the x-oai-license-identifier extension. Importing an OpenAPI document also supports reading back identifier (or x-oai-license-identifier for 3.0 documents).,> ,> typespec,> @info(#{,> license: #{ name: "MIT", identifier: "MIT" },,> }),> namespace MyService;,>

`@typespec/http-client-java` - feature ✏️

Validate Java runtime version in dependency check

`@typespec/compiler` - internal ✏️

Replace the source-map-support dependency with the native Node.js process.setSourceMapsEnabled(true) API in the CLI entrypoints.

`@typespec/tspd` - internal ✏️

Replace the source-map-support dependency with the native Node.js process.setSourceMapsEnabled(true) API in the CLI entrypoints.

`@typespec/spector` - internal ✏️

Replace the source-map-support dependency with the native Node.js process.setSourceMapsEnabled(true) API in the CLI entrypoints.

`@typespec/bundler` - internal ✏️

Replace the source-map-support dependency with the native Node.js process.setSourceMapsEnabled(true) API in the CLI entrypoints.

`@typespec/graphql` - internal ✏️

Replace the source-map-support dependency with the native Node.js process.setSourceMapsEnabled(true) API in the CLI entrypoints.

`@typespec/openapi3` - feature ✏️

Extend the enum-strategy: annotated emitter option to unions of literals. When set to annotated, a union whose variants are literals is emitted as a oneOf/anyOf of const subschemas with per-variant title/description taken from @summary and @doc, instead of collapsing to a single lossy enum. Supported for OpenAPI 3.1.0 and above; emitting with OpenAPI 3.0.0 falls back to the default form and reports a warning.,> ,> For example, the following TypeSpec:,> ,> typespec,> /** Set of known error types. */,> union ErrorType {,> /** Common error for a bad request. */,> @summary("CommonBadRequest"),> commonBadRequest: "https://example.com/errors/bad-request",,> ,> /** The request body could not be parsed. */,> @summary("InvalidBody"),> invalidBody: "https://example.com/errors/invalid-body",,> },> ,> ,> emits:,> ,> yaml,> ErrorType:,> description: Set of known error types.,> anyOf:,> - const: https://example.com/errors/bad-request,> title: CommonBadRequest,> description: Common error for a bad request.,> - const: https://example.com/errors/invalid-body,> title: InvalidBody,> description: The request body could not be parsed.,> ,> ,> Use @oneOf on the union to emit oneOf instead of anyOf.

`@typespec/http` - feature ✏️

Add scope support to OpenIdConnectAuth. The model now accepts an optional Scopes template parameter (OpenIdConnectAuth<ConnectUrl, Scopes>) and the OpenAPI3 emitter emits those scopes on each operation's openIdConnect security requirement. The scheme object itself remains unchanged (scopes are discovered via the openIdConnectUrl). Existing OpenIdConnectAuth<Url> usages are unaffected.

`@typespec/openapi3` - feature ✏️

Add scope support to OpenIdConnectAuth. The model now accepts an optional Scopes template parameter (OpenIdConnectAuth<ConnectUrl, Scopes>) and the OpenAPI3 emitter emits those scopes on each operation's openIdConnect security requirement. The scheme object itself remains unchanged (scopes are discovered via the openIdConnectUrl). Existing OpenIdConnectAuth<Url> usages are unaffected.

`@typespec/bundle-uploader` - internal ✏️

Extend publish pipeline to upload emitter bundles to Playground storage account. Update Python emitter to be browser-compatible for use in the TypeSpec playground.

`typespec-vscode` - internal ✏️

Reuse the compiler's UriTemplateSource.loadIndex() to load tsp init template indexes instead of the extension's own file/URL reading and JSON parsing, unifying how core and configured templates are loaded.

`@typespec/compiler` - feature ✏️

Add a docs field to linter rule and diagnostic definitions to provide extended reference documentation. The value can be an inline markdown string or a FileRef created with fileRef.fromPackageRoot("src/rules/my-rule.md"), which is read lazily by tooling so it stays safe to bundle for the browser.,> ,> ts,> export const myRule = createRule({,> name: "my-rule",,> severity: "warning",,> description: "Short description.",,> docs: fileRef.fromPackageRoot("src/rules/my-rule.md"),,> messages: {,> /* ... */,> },,> });,>

`@typespec/tspd` - feature ✏️

tspd doc now generates a documentation page per linter rule (reference/rules/<name>.md) and per diagnostic (reference/diagnostics/<code>.md), sourced from the docs field on the rule and diagnostic definitions. A documentation-missing warning is reported for any linter rule or diagnostic that does not provide documentation.

`@typespec/http` - internal ✏️

Provide extended documentation for the op-reference-container-route linter rule via a co-located markdown file.

`@typespec/compiler` - internal ✏️

Remove the unused backupPath fallback argument from the internal runScript helper

`@typespec/spec-dashboard` - internal ✏️

Add coverage overview component and emitter display name support

`@typespec/http-specs` - feature ✏️

Add SSE tests

`@typespec/spec-api` - feature ✏️

Add streamChunks support to MockBody for chunked SSE streaming in mock responses

`@typespec/spector` - feature ✏️

Support chunked streaming via streamChunks in mock response body

`@typespec/compiler` - feature ✏️

createTester now mounts each discovered library's tspconfig.yaml into the virtual file system, so experimental features a library opts into (e.g. auto-decorators) are honored when compiling against the tester.

`@typespec/tspd` - feature ✏️

tspd gen-extern-signature now also generates a typed setter (e.g. setMyFlag, setMyLabel) for each auto decorator, alongside the existing is*/get* readers.

`@typespec/tspd` - feature ✏️

Add a --rules-dir option (and rulesDir API option) to tspd doc to control where per-rule reference pages are written. Defaults to rules (relative to --output-dir); can be set to a path escaping the output dir (e.g. ../rules) to keep rule pages outside the generated reference folder.

`@typespec/http-client-java` - dependencies ✏️

Update js-yaml dependency to ^4.2.0

dependabot Bot and others added 30 commits June 1, 2026 20:06

Stub property type (microsoft#10798)

d9b410d

Co-authored-by: Qiaoqiao Zhang <55688292+qiaozha@users.noreply.github.com>

Upgrade dependencies (microsoft#10853)

45cda59

[python] fix CI (microsoft#10874)

f841dc5

Publish/python/multipart fix (microsoft#10871)

3c23dd2

Co-authored-by: iscai-msft <isabellavcai@gmail.com> Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Revert "Fix Python emitter CI publish failure: stamp prerelease versi…

ccc3f60

…on in Build-Packages.ps1" (microsoft#10881) Reverts microsoft#10817 After discussion, we revert this PR to avoid duplicated alpha release for same python emitter content.

[python] bump tcgc (microsoft#10894)

a86245c

Co-authored-by: iscai-msft <isabellavcai@gmail.com>

Improve documentation generated for options and sub exports (microsof…

4a630c6

…t#10640)

Don't retriage on reopen (microsoft#10889)

8c7de58

timotheeguerin and others added 29 commits July 17, 2026 17:03

[specs] add sse tests (microsoft#11239)

8d47733

fixes microsoft#6870 --------- Co-authored-by: iscai-msft <isabellavcai@gmail.com> Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Bump prettier and format [skip chg] (microsoft#11332)

feafcd0

Splitting from the rest of dep upgrade as it creates a lot of diff

[python] release new version (microsoft#11333)

ef65dbd

Conversation

iscai-msft commented Jul 22, 2026

Uh oh!

github-actions Bot commented Jul 22, 2026

@typespec/http-client-java - dependencies ✏️

@typespec/http-client-java - internal ✏️

@typespec/emitter-framework - feature ✏️

@typespec/compiler - feature ✏️

@typespec/http-client-java - internal ✏️

@typespec/http-client-java - internal ✏️

@typespec/http-client-java - internal ✏️

@typespec/http-client-java - internal ✏️

@typespec/http-client-java - dependencies ✏️

@typespec/openapi3 - internal ✏️

@typespec/http-client-java - feature ✏️

@typespec/graphql - internal ✏️

@typespec/http-client-java - internal ✏️

@typespec/http-client-java - internal ✏️

@typespec/http-client-java - internal ✏️

@typespec/http-client-java - fix ✏️

@typespec/http - internal ✏️

@typespec/http-client-java - fix ✏️

typespec-vscode - fix ✏️

@typespec/http-client-java - internal ✏️

@typespec/http-client-java - internal ✏️

@typespec/http-client-java - fix ✏️

@typespec/http-client-java - dependencies ✏️

@typespec/http-client-java - internal ✏️

@typespec/http-client-java - dependencies ✏️

@typespec/http-client-java - dependencies ✏️

@typespec/http-client-java - dependencies ✏️

@typespec/http-client-java - fix ✏️

@typespec/http-client-java - feature ✏️

@typespec/http-client-java - fix ✏️

@typespec/http-client-java - fix ✏️

@typespec/http-client-java - dependencies ✏️

@typespec/http-client-java - fix ✏️

@typespec/http-client-java - fix ✏️

@typespec/http-client-java - feature ✏️

@typespec/http-client-java - feature ✏️

@typespec/http-client-java - feature ✏️

@typespec/compiler - internal ✏️

@typespec/openapi - feature ✏️

@typespec/openapi3 - feature ✏️

@typespec/http-client-java - feature ✏️

@typespec/compiler - internal ✏️

@typespec/tspd - internal ✏️

@typespec/spector - internal ✏️

@typespec/bundler - internal ✏️

@typespec/graphql - internal ✏️

@typespec/openapi3 - feature ✏️

@typespec/http - feature ✏️

@typespec/openapi3 - feature ✏️

@typespec/bundle-uploader - internal ✏️

typespec-vscode - internal ✏️

@typespec/compiler - feature ✏️

@typespec/tspd - feature ✏️

@typespec/http - internal ✏️

@typespec/compiler - internal ✏️

@typespec/spec-dashboard - internal ✏️

@typespec/http-specs - feature ✏️

@typespec/spec-api - feature ✏️

@typespec/spector - feature ✏️

@typespec/compiler - feature ✏️

@typespec/tspd - feature ✏️

@typespec/tspd - feature ✏️

@typespec/http-client-java - dependencies ✏️

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

20 participants

`@typespec/http-client-java` - dependencies ✏️

`@typespec/http-client-java` - internal ✏️

`@typespec/emitter-framework` - feature ✏️

`@typespec/compiler` - feature ✏️

`@typespec/http-client-java` - internal ✏️

`@typespec/http-client-java` - internal ✏️

`@typespec/http-client-java` - internal ✏️

`@typespec/http-client-java` - internal ✏️

`@typespec/http-client-java` - dependencies ✏️

`@typespec/openapi3` - internal ✏️

`@typespec/http-client-java` - feature ✏️

`@typespec/graphql` - internal ✏️

`@typespec/http-client-java` - internal ✏️

`@typespec/http-client-java` - internal ✏️

`@typespec/http-client-java` - internal ✏️

`@typespec/http-client-java` - fix ✏️

`@typespec/http` - internal ✏️

`@typespec/http-client-java` - fix ✏️

`typespec-vscode` - fix ✏️

`@typespec/http-client-java` - internal ✏️

`@typespec/http-client-java` - internal ✏️

`@typespec/http-client-java` - fix ✏️

`@typespec/http-client-java` - dependencies ✏️

`@typespec/http-client-java` - internal ✏️

`@typespec/http-client-java` - dependencies ✏️

`@typespec/http-client-java` - dependencies ✏️

`@typespec/http-client-java` - dependencies ✏️

`@typespec/http-client-java` - fix ✏️

`@typespec/http-client-java` - feature ✏️

`@typespec/http-client-java` - fix ✏️

`@typespec/http-client-java` - fix ✏️

`@typespec/http-client-java` - dependencies ✏️

`@typespec/http-client-java` - fix ✏️

`@typespec/http-client-java` - fix ✏️

`@typespec/http-client-java` - feature ✏️

`@typespec/http-client-java` - feature ✏️

`@typespec/http-client-java` - feature ✏️

`@typespec/compiler` - internal ✏️

`@typespec/openapi` - feature ✏️

`@typespec/openapi3` - feature ✏️

`@typespec/http-client-java` - feature ✏️

`@typespec/compiler` - internal ✏️

`@typespec/tspd` - internal ✏️

`@typespec/spector` - internal ✏️

`@typespec/bundler` - internal ✏️

`@typespec/graphql` - internal ✏️

`@typespec/openapi3` - feature ✏️

`@typespec/http` - feature ✏️

`@typespec/openapi3` - feature ✏️

`@typespec/bundle-uploader` - internal ✏️

`typespec-vscode` - internal ✏️

`@typespec/compiler` - feature ✏️

`@typespec/tspd` - feature ✏️

`@typespec/http` - internal ✏️

`@typespec/compiler` - internal ✏️

`@typespec/spec-dashboard` - internal ✏️

`@typespec/http-specs` - feature ✏️

`@typespec/spec-api` - feature ✏️

`@typespec/spector` - feature ✏️

`@typespec/compiler` - feature ✏️

`@typespec/tspd` - feature ✏️

`@typespec/tspd` - feature ✏️

`@typespec/http-client-java` - dependencies ✏️