build(deps): bump core from 6ebff38 to c58de60 [skip chg] - #5182
Merged
Timothee Guerin (timotheeguerin) merged 4 commits intoAug 7, 2026
Conversation
Bumps [core](https://github.com/microsoft/typespec) from `6ebff38` to `c58de60`. - [Release notes](https://github.com/microsoft/typespec/releases) - [Commits](microsoft/typespec@6ebff38...c58de60) --- updated-dependencies: - dependency-name: core dependency-version: c58de60f9fa281a7938fcdb09faa61be8e436c2f dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
requested review from
Mark Cowlishaw (markcowl) and
Timothee Guerin (timotheeguerin)
as code owners
August 7, 2026 13:23
|
Azure Pipelines: 1 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
Timothee Guerin (timotheeguerin)
enabled auto-merge
August 7, 2026 13:26
Timothee Guerin (timotheeguerin)
approved these changes
Aug 7, 2026
Contributor
|
❌ There is undocummented changes. Run The following packages have changes but are not documented.
Show changes |
6ebff38 to c58de606ebff38 to c58de60 [skip chg]
commit: |
Contributor
📦 Package size report25 packages changed size compared to the base branch.
20 unchanged package(s)
Packed = gzipped |
4 tasks
Timothee Guerin (timotheeguerin)
deleted the
dependabot/submodules/core-c58de60
branch
August 7, 2026 15:10
Joel Hendrix (jhendrixMSFT)
pushed a commit
to jhendrixMSFT/typespec-azure
that referenced
this pull request
Aug 7, 2026
…Azure#5184) The package size check reports noise. On [Azure#5182](Azure#5182 (comment)) — a core submodule bump — it claimed **25 packages changed size**, most by a handful of bytes. Two independent causes, both fixed here. **It measured the `core/` submodule.** Those packages are published from `microsoft/typespec`; no PR here can change their published size. They're also measured unreliably — 11 of them ship `.turbo/turbo-build.log`, which captures the compiler version banner and CLI spinner frames, so their tarball size shifts on every build (filed as microsoft/typespec#11589). Measurement is now scoped to this repo's `packages/`, taking the report from 45 packages down to the 13 we actually publish. **Rebuilding isn't byte-reproducible, so every package wobbled.** `@azure-tools/typespec-java` is the clearest case: it ships a Maven jar whose zip entries carry wall-clock build timestamps. The workflow builds head and base minutes apart, so those bytes differ while the jar's *length* doesn't — the packed size moves a few dozen bytes and the unpacked delta is exactly zero. The report duly announced it as a change. Deltas now need to clear both a byte floor and a percentage floor to count, mirroring `isNotableMetricChange` in `packages/benchmark/src/compare.ts`. Sub-threshold rows drop into the collapsed section instead of leading the comment: > 2 packages changed size, +19.99 KB (+0.1%) packed overall. | Package | Packed (base → head) | Δ Packed | Unpacked (base → head) | Δ Unpacked | | --- | --- | --- | --- | --- | | `@azure-tools/typespec-metadata` 🆕 | — → 15.91 KB | +15.91 KB (new) | — → 62.26 KB | +62.26 KB (new) | | `@azure-tools/typespec-azure-core` | 123.69 KB → 127.87 KB | +4.18 KB (+3.4%) 🔴 | 689.86 KB → 695.48 KB | +5.63 KB (+0.8%) 🔴 | <details> <summary>2 package(s) with no notable change</summary> | Package | Packed (base → head) | Δ Packed | Unpacked (base → head) | Δ Unpacked | | --- | --- | --- | --- | --- | | `@azure-tools/typespec-ts` | 524.72 KB → 524.66 KB | -58 B (-0.0%) | 2.53 MB → 2.53 MB | — | | `@azure-tools/typespec-java` | 13.51 MB → 13.51 MB | -46 B (-0.0%) | 15.03 MB → 15.03 MB | — | </details> The 🔴/🟢 markers match the benchmark comment's existing convention. I first tried real colored text via GitHub inline math, but it renders in MathJax's fonts rather than GitHub's, and it's a pattern almost no size bot uses — `preactjs/compressed-size-action`, `size-limit-action`, Codecov, BundleMon and the Next.js bot all signal direction with emoji instead. `compare.ts` no longer runs `main()` on import, so the rendering is covered by tests.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps core from
6ebff38toc58de60.Commits
c58de60json-schema: key bundled$defsentries by explicit@idto prevent silent ...41093e8fix: use compiler version for standalone CLI distribution versioning [skip ch...b3a9dc5fix(compiler): improve error message when --emit specifies an uninstalled emi...02ef0c1Enable verbatimModuleSyntax in tsconfig.base.json [skip chg] (#11521)13da410Fix doc comments that document things that don't exist in@typespec/rest(#11...df39c35Add C# HTTP server emitter to the playground (#11568)600b63aRegister JsonPatch propagators in all applicable generated C# constructors (#...fbd68c6Remove Azure-only diagnostics from Java emitter docs (#11581)205ceecFix inherited paging item lookup in C# generator (#11577)4691031Add sample metadata configuration (#11498)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 commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)