chore(deps-dev): bump the dev-dependencies group across 1 directory with 18 updates

[dependabot]

Bumps the dev-dependencies group with 18 updates in the / directory:

Package	From	To
@arethetypeswrong/cli	0.18.4	0.18.5
@changesets/cli	2.31.0	3.0.0
@cosyte/eslint-config	0.0.3	0.0.6
@cosyte/prettier-config	0.0.2	0.0.4
@cosyte/test-utils	0.0.2	0.0.4
@cosyte/tsconfig	0.0.2	0.0.4
@cosyte/tsup-config	0.0.1	0.0.3
@cosyte/vitest-config	0.0.2	0.0.4
@types/node	22.20.0	26.2.0
@vitest/coverage-v8	4.1.4	4.1.10
eslint	10.5.0	10.8.1
fast-check	3.23.2	4.9.0
prettier	3.8.3	3.9.6
simple-git-hooks	2.13.0	2.13.1
tsx	4.21.0	4.23.12
typescript	5.9.3	7.0.2
vite	7.3.6	8.2.1
vitest	4.1.4	4.1.10

Updates @arethetypeswrong/cli from 0.18.4 to 0.18.5

Changelog

Sourced from @​arethetypeswrong/cli's changelog.

0.18.5

Patch Changes

• Updated dependencies [c4be7e8]
  • @​arethetypeswrong/core@​0.18.5

Commits

• See full diff in compare view

Updates @changesets/cli from 2.31.0 to 3.0.0

Release notes

Sourced from @​changesets/cli's releases.

@​changesets/cli@​3.0.0

Major Changes

• #2128 7113c01 Thanks @​Andarist! - Renamed the changeset tag command to changeset git-tag.

• #2074 3599e47 Thanks @​bluwy! - Set supported package manager versions in "engines" field, including npm >=10.9.0, pnpm >=10.0.0, and yarn >=4.5.2.

• #1860 92b1c1b Thanks @​mixelburg! - changeset version now exits with code 1 when there are no unreleased changesets, instead of silently exiting with code 0.

  This makes it easier to detect when a version step is a no-op — for example, to prevent accidentally publishing packages with incorrect version tags when using --snapshot mode.

• #1482 df424a4 Thanks @​Andarist! - Bumped supported Node versions to ^22.11 || ^24 || >=26

• #1994 062530b Thanks @​bluwy! - The prettier option in .changeset/config.json has been removed in favor of format. format supports "auto", "prettier", "oxfmt", "deno", and "dprint", and false disables formatting. If you previously used prettier: false, migrate to format: false or remove the option to use automatic formatter detection.

• #2190 96b65ee Thanks @​bluwy! - Move versioned prerelease changesets to .changeset/pre/ folder instead of accumulating in the root and tracking the versioned changeset ids in the .changeset/pre.json file. Existing pre.json will auto-migrate to this new structure on the next run of changeset version or when calling changeset status.

  This change allows easier management of versioned prerelease changesets (for the final stable release) and current queued changesets (for the next prerelease). Changesets in .changeset/pre/ can be edited or deleted depending if it's still relevant for the final stable release of a package. There's no need to synchronize the changeset ids in pre.json if certain changesets are deleted.

• #2145 f5887ff Thanks @​Andarist! - Removed Yarn Classic support

• #2097 8c88f6a Thanks @​Andarist! - Packages with only prerelease versions published will now be published with the prerelease tag in the prerelease mode if the target registry doesn't auto-assign latest tag. npm registry itself does that and such packages will continue to be released with latest tag (and not with the configured prerelease tag).

• #1879 c76b232 Thanks @​beeequeue! - Removed warning messages about using v1 configs. They will now be silently ignored.

• #1655 db46911 Thanks @​bluwy! - Update @manypkg/get-packages which drops support for detecting packages in Bolt monorepos and adds support for npm monorepos

• #1651 e1df862 Thanks @​bluwy! - Remove support for the --sinceMaster flag for changeset status. Use --since=master or --since=main instead.

• #2117 813bbf3 Thanks @​bluwy! - Remove the pre.json initialVersions property and handling as it's unused internally

• #1961 07278a7 Thanks @​beeequeue! - CommitFunctions can now be both sync and async, and the defaultCommitFunctions are now sync.

• #1482 df424a4 Thanks @​Andarist! - From now on this package is going to be published as ES module.

• #1652 a0b5326 Thanks @​bluwy! - Remove support for the deprecated ___experimentalUnsafeOptions_WILL_CHANGE_IN_PATCH.useCalculatedVersionForSnapshots config. The snapshot.useCalculatedVersion config should be used instead.

• #2186 3910adf Thanks @​Andarist! - Private packages are no longer versioned by default. Set privatePackages to true to opt into versioning and tagging them, or set privatePackages.version to true to version them without tagging.

• #1879 c76b232 Thanks @​beeequeue! - Migrated from enquirer + @inquirer/launch-editor to @clack/prompts + launch-editor.

  This means the CLI flows will have minor changes, but they are largely the same.

  This change also fixes various issues related to enquirer like cancelling prompts crashing the CLI.

• #2090 3aae903 Thanks @​beeequeue! - Peer dependencies now bump packages that depend on them by patch instead of major.

  This means a peer dependency update is no longer assumed (forced) to be a breaking change.

  If the dependent package is not compatible with the peer's new release you should manually add a major changeset describing why and how to migrate.

... (truncated)

Changelog

Sourced from @​changesets/cli's changelog.

3.0.0

Major Changes

• #2128 7113c01 Thanks @​Andarist! - Renamed the changeset tag command to changeset git-tag.

• #2074 3599e47 Thanks @​bluwy! - Set supported package manager versions in "engines" field, including npm >=10.9.0, pnpm >=10.0.0, and yarn >=4.5.2.

• #1860 92b1c1b Thanks @​mixelburg! - changeset version now exits with code 1 when there are no unreleased changesets, instead of silently exiting with code 0.

  This makes it easier to detect when a version step is a no-op — for example, to prevent accidentally publishing packages with incorrect version tags when using --snapshot mode.

• #1482 df424a4 Thanks @​Andarist! - Bumped supported Node versions to ^22.11 || ^24 || >=26

• #1994 062530b Thanks @​bluwy! - The prettier option in .changeset/config.json has been removed in favor of format. format supports "auto", "prettier", "oxfmt", "deno", and "dprint", and false disables formatting. If you previously used prettier: false, migrate to format: false or remove the option to use automatic formatter detection.

• #2190 96b65ee Thanks @​bluwy! - Move versioned prerelease changesets to .changeset/pre/ folder instead of accumulating in the root and tracking the versioned changeset ids in the .changeset/pre.json file. Existing pre.json will auto-migrate to this new structure on the next run of changeset version or when calling changeset status.

  This change allows easier management of versioned prerelease changesets (for the final stable release) and current queued changesets (for the next prerelease). Changesets in .changeset/pre/ can be edited or deleted depending if it's still relevant for the final stable release of a package. There's no need to synchronize the changeset ids in pre.json if certain changesets are deleted.

• #2145 f5887ff Thanks @​Andarist! - Removed Yarn Classic support

• #2097 8c88f6a Thanks @​Andarist! - Packages with only prerelease versions published will now be published with the prerelease tag in the prerelease mode if the target registry doesn't auto-assign latest tag. npm registry itself does that and such packages will continue to be released with latest tag (and not with the configured prerelease tag).

• #1879 c76b232 Thanks @​beeequeue! - Removed warning messages about using v1 configs. They will now be silently ignored.

• #1655 db46911 Thanks @​bluwy! - Update @manypkg/get-packages which drops support for detecting packages in Bolt monorepos and adds support for npm monorepos

• #1651 e1df862 Thanks @​bluwy! - Remove support for the --sinceMaster flag for changeset status. Use --since=master or --since=main instead.

• #2117 813bbf3 Thanks @​bluwy! - Remove the pre.json initialVersions property and handling as it's unused internally

• #1961 07278a7 Thanks @​beeequeue! - CommitFunctions can now be both sync and async, and the defaultCommitFunctions are now sync.

• #1482 df424a4 Thanks @​Andarist! - From now on this package is going to be published as ES module.

• #1652 a0b5326 Thanks @​bluwy! - Remove support for the deprecated ___experimentalUnsafeOptions_WILL_CHANGE_IN_PATCH.useCalculatedVersionForSnapshots config. The snapshot.useCalculatedVersion config should be used instead.

• #2186 3910adf Thanks @​Andarist! - Private packages are no longer versioned by default. Set privatePackages to true to opt into versioning and tagging them, or set privatePackages.version to true to version them without tagging.

• #1879 c76b232 Thanks @​beeequeue! - Migrated from enquirer + @inquirer/launch-editor to @clack/prompts + launch-editor.

  This means the CLI flows will have minor changes, but they are largely the same.

  This change also fixes various issues related to enquirer like cancelling prompts crashing the CLI.

• #2090 3aae903 Thanks @​beeequeue! - Peer dependencies now bump packages that depend on them by patch instead of major.

  This means a peer dependency update is no longer assumed (forced) to be a breaking change.

... (truncated)

Commits

• f442221 Version Packages (#2235)
• e3facad Version Packages (next) (#2228)
• c98af4c Do not bump ignored independent packages when exiting pre mode (#2092)
• 496ca21 Build(deps-dev): Bump the development-dependencies group with 6 updates (#2225)
• d1053ac Build(deps): Bump the production-dependencies group across 1 directory with 2...
• 68ea6ec Fix linked and fixed glob patterns expansion (#2222)
• c1b6f8c fix missing coloring of name (#2218)
• a53d1f8 Remove old atlaskit changelogs (#2217)
• 7bcb2d2 Build(deps-dev): Bump the development-dependencies group across 1 directory w...
• baa658d Version Packages (next) (#2192)
• Additional commits viewable in compare view

Updates @cosyte/eslint-config from 0.0.3 to 0.0.6

Release notes

Sourced from @​cosyte/eslint-config's releases.

@​cosyte/eslint-config@​0.0.6

The bundled CHANGELOG.md no longer heads already-shipped content [Unreleased].

Every section now carries the version it shipped in, dated from that release's tag, so a reader of the published tarball can tell which release a given entry belongs to. Previously the newest entries sat under [Unreleased] in the file that shipped, which meant each release republished the previous release's notes under a heading saying they had not shipped yet.

Nothing else in the tarball changes: no rule, setting, compiler option, build option, or runner behaviour is different in any of the six packages.

Install

npm install @cosyte/eslint-config@0.0.6

npm: https://www.npmjs.com/package/@​cosyte/eslint-config/v/0.0.6

@​cosyte/eslint-config@​0.0.5

Changed

Documentation and source comments were repunctuated to drop em dashes, in line with the cosyte brand voice.

No rule, option, or behaviour change. The README ships inside the tarball and renders on the npm package page, which is why a text-only change is versioned at all. If you are upgrading from 0.0.4, nothing you configure or lint changes.

@​cosyte/eslint-config@​0.0.4

Changelog

All notable changes to @cosyte/eslint-config are documented here, following Keep a Changelog. Versions are managed with Changesets; this file is hand-maintained (Changesets' own changelog generation is disabled). The package stays on the 0.0.x-until-first-alpha ladder.

[Unreleased]

Added

• Application mode: cosyte(rootDir, { library: false }) drops the JSDoc + @example gate and no-console while keeping every type-safety rule (no any, no unjustified casts, exhaustiveness, strict imports). Libraries (the default, library: true) are unchanged. This makes applications — like the pathways engine — first-class consumers of the one shared config instead of forking it: an app has no published API surface to document and legitimately logs.

[0.0.3] - 2026-06-25

Changed

• ESLint 10 baseline: @eslint/js ^10, eslint-plugin-jsdoc ^63, typescript-eslint ^8.62, eslint-config-prettier ^10.1. The eslint peer accepts ^9 || ^10 during the suite's migration

... (truncated)

Changelog

Sourced from @​cosyte/eslint-config's changelog.

Changelog

All notable changes to @cosyte/eslint-config are documented here, following Keep a Changelog. Versions are managed with Changesets; this file is hand-maintained (Changesets' own changelog generation is disabled). The package stays on the 0.0.x-until-first-alpha ladder.

Because the generator is disabled, [Unreleased] is promoted to a version heading BY HAND, in the pull request that adds the changeset. Nothing does it automatically. Until 2026-08-04 nothing did it at all, so shipped content stayed under [Unreleased] and every release republished it.

[Unreleased]

Changed

• The sections below were relabelled: content that had already shipped was still sitting under [Unreleased], so each release republished it. Every section now carries the version it shipped in. No rule, option, or behaviour change; the CHANGELOG.md inside the published tarball is the only thing that differs.

[0.0.5] - 2026-07-31

Changed

• Documentation and source comments no longer use em dashes, in line with the cosyte brand voice. No rule, option, or behaviour change.

[0.0.4] - 2026-06-26

Added

• Application mode: cosyte(rootDir, { library: false }) drops the JSDoc + @example gate and no-console while keeping every type-safety rule (no any, no unjustified casts, exhaustiveness, strict imports). Libraries (the default, library: true) are unchanged. This makes applications, like the pathways engine, first-class consumers of the one shared config instead of forking it: an app has no published API surface to document and legitimately logs.

Commits

• 3766366 Version Packages (#46)
• 89cc33f fix(release): close the three ways this repo's releases lied about themselves...
• 89d5d06 Version Packages (#39)
• 1f35b93 feat(brand): sweep every em dash and land the no-emdash gate in the same comm...
• 2e13eeb docs(config): date test-utils 0.0.1 + eslint-config 0.0.4 (2026-06-26)
• 71c1267 Version Packages (#2)
• 133d856 docs(config): date the published CHANGELOG entries (2026-06-25 batch)
• 4af165e feat(eslint-config): add application mode (library: false)
• See full diff in compare view

Updates @cosyte/prettier-config from 0.0.2 to 0.0.4

Release notes

Sourced from @​cosyte/prettier-config's releases.

@​cosyte/prettier-config@​0.0.4

The bundled CHANGELOG.md no longer heads already-shipped content [Unreleased].

Every section now carries the version it shipped in, dated from that release's tag, so a reader of the published tarball can tell which release a given entry belongs to. Previously the newest entries sat under [Unreleased] in the file that shipped, which meant each release republished the previous release's notes under a heading saying they had not shipped yet.

Nothing else in the tarball changes: no rule, setting, compiler option, build option, or runner behaviour is different in any of the six packages.

Install

npm install @cosyte/prettier-config@0.0.4

npm: https://www.npmjs.com/package/@​cosyte/prettier-config/v/0.0.4

@​cosyte/prettier-config@​0.0.3

Changed

Documentation was repunctuated to drop em dashes, in line with the cosyte brand voice.

No setting change. The README ships inside the tarball and renders on the npm package page, which is why a text-only change is versioned at all. If you are upgrading from 0.0.2, your formatting output is unchanged.

Changelog

Sourced from @​cosyte/prettier-config's changelog.

Changelog

All notable changes to @cosyte/prettier-config are documented here, following Keep a Changelog. Versions are managed with Changesets; this file is hand-maintained (Changesets' own changelog generation is disabled). The package stays on the 0.0.x-until-first-alpha ladder.

Because the generator is disabled, [Unreleased] is promoted to a version heading BY HAND, in the pull request that adds the changeset. Nothing does it automatically. Until 2026-08-04 nothing did it at all, so shipped content stayed under [Unreleased] and every release republished it.

[Unreleased]

Changed

• The sections below were relabelled: content that had already shipped was still sitting under [Unreleased], so each release republished it. Every section now carries the version it shipped in. No setting change; the CHANGELOG.md inside the published tarball is the only thing that differs.

[0.0.3] - 2026-07-31

Changed

• Documentation no longer uses em dashes, in line with the cosyte brand voice. No setting change.

Commits

• 3766366 Version Packages (#46)
• 89cc33f fix(release): close the three ways this repo's releases lied about themselves...
• 89d5d06 Version Packages (#39)
• 1f35b93 feat(brand): sweep every em dash and land the no-emdash gate in the same comm...
• 133d856 docs(config): date the published CHANGELOG entries (2026-06-25 batch)
• See full diff in compare view

Updates @cosyte/test-utils from 0.0.2 to 0.0.4

Release notes

Sourced from @​cosyte/test-utils's releases.

@​cosyte/test-utils@​0.0.4

PERF-P2: add @cosyte/test-utils/perf, the throughput scaling gate.

A new subpath export, and a sixth runner family alongside the conformance runners on the root entry. It exists so every @cosyte/* package can prove, in its own CI and without bespoke code, that it has not silently acquired an algorithmic-complexity regression. Zero dependencies, hand-rolled on node:perf_hooks.

• scalingGate(options): takes a workload generator and a parse function (never a file path, which is what keeps PHI out of the benchmark path by construction), does time-budgeted warmup with a stability rule, sampling, and sink accumulation, then asserts RATIO_FLOOR ≤ min(scaled)/min(base) ≤ RATIO_CEILING on two axes.
• Both axes, and size-scaling is not optional. count scales the number of inputs at fixed length; size scales each input's length at fixed count. An O(n²)-in-length tokenizer is invisible to the count axis by construction: at fixed message size a quadratic parser still scores ≈4 there , so there is no way to ask for one axis.
• assertScalingGateFires(options, injection): the per-package self-check, and the load-bearing half. The ceiling of 8 sits between a constant (the worst false alarm across 3,200 clean ratios, 6.649) and a non-constant: the weakest real O(n²) signal climbs 4.69 → 8.09 → 8.84 → 10.68 as the base fixture grows 125 → 250 → 500 → 1000 segments. At the smallest, a genuine quadratic is inside the noise and the gate reads green while broken. The self-check takes the same options object the real gate is given, so "run it at the sizes your real gate uses" is structural rather than remembered, and it fails the build when the fixture is too small. It also checks the clean parse can produce a ratio at those sizes, not just the regressed one, since the regressed parse is the slower of the two and would otherwise mask a permanently-skipping gate.
• Fail-safe. Typed, loud skips (phase-too-short, warmup-unstable) on stderr with status: "skipped", a measurement never reports a confident wrong answer, and a skip is not a pass. Both bounds are hard failures. The floor's claim is deliberately narrow: it catches the two phases received the same workload, not dead-code elimination, which stays at ≈4 on the count axis and is prevented structurally by the sink.
• PERF_CONTRACT: the frozen constants, readable, printable, and deliberately not overridable.

Every constant is fixed by documentation/decisions/0001-perf-measurement-contract.md, each tagged measured or judgement. What it does not catch, stated because it will be quoted: constant-factor regressions (a 10% slowdown passes and always will: from a single cloud instance only 17–22% of configurations reliably detect one), complexity regressions whose fixture is too small, and anything that only manifests under real I/O, network or concurrency.

No change to the root entry point: a parser importing the conformance runners does not pull node:perf_hooks in with them.

One limitation this slice measured rather than inherited, and which every adopting package needs: the ceiling is calibrated to a runner class. Across three 200-run sweeps on a CPU-quota-throttled container the gate fired on a linear workload 4 times in 600 runs, at ratios of 8.94–11.01: above the weakest real O(n²) signal at hl7's own fixture size (8.84). A same-process ratio cancels JIT state, but the two phases are separated in time and a cgroup's throttling state changes between them. So assertScalingGateFires proves your fixture is big enough and says nothing about whether your runner is quiet enough; establish both before adopting.

Install

... (truncated)

Changelog

Sourced from @​cosyte/test-utils's changelog.

Changelog

All notable changes to @cosyte/test-utils are documented here, following Keep a Changelog. Versions are managed with Changesets; this file is hand-maintained (Changesets' own changelog generation is disabled). The package stays on the 0.0.x-until-first-alpha ladder.

Because the generator is disabled, [Unreleased] is promoted to a version heading BY HAND, in the pull request that adds the changeset. Nothing does it automatically. Until 2026-08-04 nothing did it at all, so shipped content stayed under [Unreleased] and every release republished it.

[Unreleased]

Added

• @cosyte/test-utils/perf: the throughput scaling gate (PERF-P2). A new subpath export, a sixth runner family alongside the conformance runners. It exists so every @cosyte/* package can prove, in its own CI and without bespoke code, that it has not silently acquired an algorithmic-complexity regression. Zero dependencies, hand-rolled on node:perf_hooks, that question is closed (founder, 2026-07-25) and the reasons are in ADR 0001. New exports:
  • scalingGate(options): takes a workload generator and a parse function, does time-budgeted warmup, sampling and sink accumulation, and asserts RATIO_FLOOR ≤ min(scaled)/min(base) ≤ RATIO_CEILING on two axes.
  • assertScalingGateFires(options, injection): the per-package self-check.
  • PERF_CONTRACT: the frozen constants, readable and deliberately not overridable.
  • perfSink: the accumulator the measured loop sums into.
• Both axes, and size-scaling is not optional. count scales the number of inputs at fixed length; size scales each input's length at fixed count. An O(n²)-in-length tokenizer is invisible to the count axis by construction: at fixed message size a quadratic parser still scores ≈4 there, so there is no way to ask for one axis.
• The self-check, which is the load-bearing half. The ceiling of 8 is derived from a constant (the worst false alarm across 3,200 clean ratios, 6.649) and a non-constant (the weakest real O(n²) signal, which climbs 4.69 → 8.09 → 8.84 → 10.68 as the base fixture grows 125 → 250 → 500 → 1000 segments). Below about 250 base segments a genuine quadratic sits inside the noise and the gate reads green while broken. assertScalingGateFires takes the same options object the real gate is given, so "run the self-check at the sizes your real gate uses" is structural rather than a thing you remember to do, and it fails the build when the fixture is too small.
• The fail-safe: typed, loud skips. phase-too-short (base min under MIN_PHASE_MS) and warmup-unstable (never reached steady state) write the full diagnostic to stderr and return status: "skipped". A measurement never reports a confident wrong answer, and a skip is not a pass. Both bounds are hard failures: the ceiling catches the complexity regression, the floor catches the two phases having received the same workload. The floor deliberately does not claim to catch dead-code elimination, that stays at ≈4 on the count axis and is prevented structurally by the sink instead.
• PHI by construction. The runner takes a generator function, never a file path, so inputs are synthetic and produced in-process. Every diagnostic (failure, skip and report alike) carries sizes, counts, ratios and sample vectors, and never echoes input content.
• test:perf, a second non-instrumented test invocation (vitest.perf.config.ts), with test/perf/timed/** excluded from the default test run. ADR 0001 §6: @vitest/coverage-v8 drives V8's kBlockCount precise coverage, compiling an effectful counter into the measured function body

... (truncated)

Commits

• 3318238 Version Packages (#51)
• 10d15bf PERF-P2: @cosyte/test-utils/perf, the throughput scaling gate (#34)
• c6b6c99 fix(attw): the post-check reads attw's JSON, not its prose (ATTW-CONFIG-ROUTE...
• 3766366 Version Packages (#46)
• 84d0224 fix(attw): the gate's nested npm pack no longer inherits a dry run (CONFIG-PR...
• 89cc33f fix(release): close the three ways this repo's releases lied about themselves...
• 702fd2a fix(template): close both re-minted gate holes at the source (TEMPLATE-REMINT...
• 7461b0e fix(attw): the publish gate exits 0 on an untyped pack, in both manifests (#42)
• See full diff in compare view

Updates @cosyte/tsconfig from 0.0.2 to 0.0.4

Release notes

Sourced from @​cosyte/tsconfig's releases.

@​cosyte/tsconfig@​0.0.4

The bundled CHANGELOG.md no longer heads already-shipped content [Unreleased].

Every section now carries the version it shipped in, dated from that release's tag, so a reader of the published tarball can tell which release a given entry belongs to. Previously the newest entries sat under [Unreleased] in the file that shipped, which meant each release republished the previous release's notes under a heading saying they had not shipped yet.

Nothing else in the tarball changes: no rule, setting, compiler option, build option, or runner behaviour is different in any of the six packages.

Install

npm install @cosyte/tsconfig@0.0.4

npm: https://www.npmjs.com/package/@​cosyte/tsconfig/v/0.0.4

@​cosyte/tsconfig@​0.0.3

Changed

Documentation was repunctuated to drop em dashes, in line with the cosyte brand voice.

No compiler-option change. The README ships inside the tarball and renders on the npm package page, which is why a text-only change is versioned at all. If you are upgrading from 0.0.2, your build output is unchanged.

Changelog

Sourced from @​cosyte/tsconfig's changelog.

Changelog

All notable changes to @cosyte/tsconfig are documented here, following Keep a Changelog. Versions are managed with Changesets; this file is hand-maintained (Changesets' own changelog generation is disabled). The package stays on the 0.0.x-until-first-alpha ladder.

Because the generator is disabled, [Unreleased] is promoted to a version heading BY HAND, in the pull request that adds the changeset. Nothing does it automatically. Until 2026-08-04 nothing did it at all, so shipped content stayed under [Unreleased] and every release republished it.

[Unreleased]

Changed

• The sections below were relabelled: content that had already shipped was still sitting under [Unreleased], so each release republished it. Every section now carries the version it shipped in. No compiler-option change; the CHANGELOG.md inside the published tarball is the only thing that differs.

[0.0.3] - 2026-07-31

Changed

• Documentation no longer uses em dashes, in line with the cosyte brand voice. No compiler-option change.

Commits

• 3766366 Version Packages (#46)
• 89cc33f fix(release): close the three ways this repo's releases lied about themselves...
• 89d5d06 Version Packages (#39)
• 1f35b93 feat(brand): sweep every em dash and land the no-emdash gate in the same comm...
• 133d856 docs(config): date the published CHANGELOG entries (2026-06-25 batch)
• See full diff in compare view

Updates @cosyte/tsup-config from 0.0.1 to 0.0.3

Release notes

Sourced from @​cosyte/tsup-config's releases.

@​cosyte/tsup-config@​0.0.3

The bundled CHANGELOG.md no longer heads already-shipped content [Unreleased].

Every section now carries the version it shipped in, dated from that release's tag, so a reader of the published tarball can tell which release a given entry belongs to. Previously the newest entries sat under [Unreleased] in the file that shipped, which meant each release republished the previous release's notes under a heading saying they had not shipped yet.

Nothing else in the tarball changes: no rule, setting, compiler option, build option, or runner behaviour is different in any of the six packages.

Install

npm install @cosyte/tsup-config@0.0.3

npm: https://www.npmjs.com/package/@​cosyte/tsup-config/v/0.0.3

@​cosyte/tsup-config@​0.0.2

Changed

Documentation was repunctuated to drop em dashes, in line with the cosyte brand voice.

No build-option change. The README ships inside the tarball and renders on the npm package page, which is why a text-only change is versioned at all. If you are upgrading from 0.0.1, your bundles are unchanged.

Changelog

Sourced from @​cosyte/tsup-config's changelog.

Changelog

All notable changes to @cosyte/tsup-config are documented here, following Keep a Changelog. Versions are managed with Changesets; this file is hand-maintained (Changesets' own changelog generation is disabled). The package stays on the 0.0.x-until-first-alpha ladder.

Because the generator is disabled, [Unreleased] is promoted to a version heading BY HAND, in the pull request that adds the changeset. Nothing does it automatically. Until 2026-08-04 nothing did it at all, so shipped content stayed under [Unreleased] and every release republished it.

[Unreleased]

Changed

• The sections below were relabelled: content that had already shipped was still sitting under [Unreleased], so each release republished it. Every section now carries the version it shipped in. No build-option change; the CHANGELOG.md inside the published tarball is the only thing that differs.

[0.0.2] - 2026-07-31

Changed

• Documentation no longer uses em dashes, in line with the cosyte brand voice. No build-option change.

Commits

• 3766366 Version Packages (#46)
• 89cc33f fix(release): close the three ways this repo's releases lied about themselves...
• 89d5d06 Version Packages (#39)
• 1f35b93 feat(brand): sweep every em dash and land the no-emdash gate in the same comm...
• 133d856 docs(config): date the published CHANGELOG entries (2026-06-25 batch)
• See full diff in compare view

Updates @cosyte/vitest-config from 0.0.2 to 0.0.4

Release notes

Sourced from @​cosyte/vitest-config's releases.

@​cosyte/vitest-config@​0.0.4

The bundled CHANGELOG.md no longer heads already-shipped content [Unreleased].

Every section now carries the version it shipped in, dated from that release's tag, so a reader of the published tarball can tell which release a given entry belongs to. Previously the newest entries sat under [Unreleased] in the file that shipped, which meant each release republished the previous release's notes under a heading saying they had not shipped yet.

Nothing else in the tarball changes: no rule, setting, compiler option, build option, or runner behaviour is different in any of the six packages.

Install

npm install @cosyte/vitest-config@0.0.4

npm: https://www.npmjs.com/package/@​cosyte/vitest-config/v/0.0.4

@​cosyte/vitest-config@​0.0.3

Added

vite is now declared as a peer dependency (^6 || ^7 || ^8). Vitest 4 requires vite 6 or newer, and without this declaration a resolver could keep an incompatible vite 5, which is missing the ./module-runner export. If your install previously resolved vite 5 alongside this config, expect a peer warning telling you to upgrade.

A doc/code-agreement harness on a new @cosyte/vitest-config/snippets subpath: docSnippetSuite(), plus the primitives it is built from (extractRunnableSnippets, rewriteAssertions, remapImports, runSnippet).

It extracts every fenced ```ts runnable block from a package's docs-content/, compiles it, executes it against the package, and asserts its inline // => value results. It is the documentation analog of the conformance runners: a green docs build can no longer carry a snippet that silently disagrees with the code.

It is devDependency-only, and Vitest is already a peer, so it adds no new dependency.

Changed

Documentation and source comments were repunctuated to drop em dashes, in line with the cosyte brand voice. No config or behaviour change.

Changelog

Sourced from @​cosyte/vitest-config's changelog.

Changelog

All notable changes to @cosyte/vitest-config are documented here, following Keep a Changelog. Versions are managed with Changesets; this file is hand-maintained (Changesets' own changelog generation is disabled). The package stays on the 0.0.x-until-first-alpha ladder.

Because the generator is disabled, [Unreleased] is promoted to a version heading BY HAND, in the pull request that adds the changeset. Nothing does it automatically. Until 2026-08-04 nothing did it at all, so shipped content stayed under [Unreleased] and every release republished it.

[Unreleased]

Changed

• The sections below were relabelled: content that had already shipped was still sitting under [Unreleased], so each release republished it. Every section now carries the version it shipped in. No config or behaviour change; the CHANGELOG.md inside the published tarball is the only thing that differs.

[0.0.3] - 2026-07-31

Changed

• Documentation and source comments no longer use em dashes, in line with the cosyte brand voice. No config or behaviour change.

Commits

• 3766366 Version Packages (#46)
• 89cc33f fix(release): close the three ways this repo's releases lied about themselves...
• 89d5d06 Version Packages (#39)
• 1f35b93 feat(brand): sweep every em dash and land the no-emdash gate in the same comm...
• See full diff in compare view

Updates @types/node from 22.20.0 to 26.2.0

Commits

• See full diff in compare view

Updates @vitest/coverage-v8 from 4.1.4 to 4.1.10

Release notes

Sourced from @​vitest/coverage-v8's releases.

v4.1.10

   🐞 Bug Fixes

• browser: Check fs access in builtin commands [backport to v4]  -  by @​hi-ogawa, Hiroshi Ogawa and OpenCode (claude-opus-4-8) in vitest-dev/vitest#10680 (5c18d)
• vm: Fix external module resolve error with deps optimizer query for encoded URI [backport to v4]  -  by @​SveLil and @​hi-ogawa in vitest-dev/vitest#10661 (bae52)

    View changes on GitHub

v4.1.9

🐞 Bug Fixes

• Fix importOriginal with optimizer and query import [backport to v4] - by Hiroshi Ogawa, David Harris, Codexand Vladimir in vitest-dev/vitest#10546 (a5180)
• browser:
  • Wait for orchestrator readiness before resolving browser sessions [backport to v4] - by Vladimir and Séamus O'Connor in vitest-dev/vitest#10555 (7fb29)
  • Wait for iframe tester readiness before preparing [backport to v4] - by Vladimir and Séamus O'Connor in