build(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	2.31.1
@cosyte/eslint-config	0.0.4	0.0.6
@cosyte/prettier-config	0.0.2	0.0.4
@cosyte/test-utils	0.0.1	0.0.3
@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.1	26.1.2
@vitest/coverage-v8	4.1.4	4.1.10
eslint	10.5.0	10.8.0
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.7
typescript	5.9.3	7.0.2
vite	7.3.6	8.2.0
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 2.31.1

Release notes

Sourced from @​changesets/cli's releases.

@​changesets/cli@​2.31.1

Patch Changes

• #2159 15cf592 Thanks @​ingvaldlorentzen! - Fixed already-published version detection with npm 12, which always wraps successful npm info --json output in an array. The unwrapped output made changeset publish treat every package as unpublished and fail attempting to republish existing versions.

Commits

• a897bb8 Use a different publish tag for maintenance/v2 branch (#2162)
• e8650b9 Version Packages (#2161)
• 15cf592 Fixed handling of the npm 12 info output (#2159)
• 9f2cb2a Configure Changesets for maintenance/v2 line (#2076)
• 97247cb Change allowed publish pattern to maintenance/v* given rulesets behavior (#...
• 13286a8 Build(deps): Bump the github-actions group across 1 directory with 3 updates ...
• 8f6acd6 Update dependabot group to exclude major (#2067)
• c70c675 Setup backport workflow and sync next setup (#2057)
• 9672019 Remove SECURITY.md to defer to .github (#2055)
• 18e1661 Use internal bot for versioning (#2039)
• Additional commits viewable in compare view

Updates @cosyte/eslint-config from 0.0.4 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.

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.

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)
• 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.1 to 0.0.3

Release notes

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

@​cosyte/test-utils@​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/test-utils@0.0.3

npm: https://www.npmjs.com/package/@​cosyte/test-utils/v/0.0.3

@​cosyte/test-utils@​0.0.2

Added

assertNoDiagnosticPhiLeak: a runner that proves consumer-controlled input does not echo into a diagnostic surface.

For each slot you declare, it sweeps every diagnostic message, the whole diagnostic rendered as JSON, as util.inspect and by a walk of the object graph, err.message, err.stack, the thrown value itself, and every structural identifier you enumerate on the parsed model. The walk is what reaches a nested toString, raw bytes attached as context, and entries past inspect's truncation ceilings, none of which either summary rendering shows. Matching is case-insensitive.

What it proves, stated narrowly:

For each declared slot, no verbatim echo of four or more bytes of the planted value appears in any swept surface, and the slot provably reached the diagnostic it names.

It does not prove the absence of a re-encoded echo, an echo shorter than four bytes, a leak carried only as a number, a leak through an undeclared slot, or reach in strict mode.

Each slot names the diagnostic code it expects, and that code must appear in lenient mode. Counting diagnostics is not enough: an unrelated warning can otherwise stand in for the one the slot exists to trigger, leaving the leaking branch unentered. Reach is lenient-only, because a strict mode throws on the first deviation and only one slot could ever be that deviation.

getDiagnostics, getModelIdentifiers and parseStrict are required, not defaulted. () => [] and null are legitimate answers; silence is not, so a parser cannot go green on a model the runner only half-read.

checkLengthInvariance is opt-in. It catches a re-encoded echo, but a diagnostic carrying an input-derived number (a position column gaining digits, a byte count) grows the same way and is correct.

assertNoSecretLeak is unchanged. It answers a different question, whether a Secret<T> wrapper resists stringification, and the docs now say so at the point of import: importing one is not coverage for the other.

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

• 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)
• 89d5d06 Version Packages (#39)
• f32e7dd fix(release): stop prepublishOnly running a tool that packs (#40)
• 3be452e feat(test-utils): prove input never echoes to a diagnostic surface (#38)
• 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)
• 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.1 to 26.1.2

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 vitest-dev/vitest#10497 and vitest-dev/vitest#10556 (fbc62)
• mocker:
  • Hoist vi.mock() for vite-plus/test imports [backport to v4] - by Hiroshi Ogawa, LongYinan, Claude Opus 4.8 and Vladimir in vitest-dev/vitest#10548 (2c955)
• pool:
  • Prevent test run hang on worker crash [backport to v4] - by Ari Perkkiö and Jattioui Ismail in vitest-dev/vitest#10543 and vitest-dev/vitest#10564 (934b0)

View changes on GitHub

v4.1.8

   🐞 Bug Fixes

• browser:
  • Disable client cdp API when allowWrite/allowExec: false [backport to v4]  -  by @​hi-ogawa and Codex in vitest-dev/vitest#10450 (e4067)
  • Remove orphaned Playwright route when same module is mocked via multiple ids [backport to v4]  -  by @​toxik and @​Zelys-DFKH in vitest-dev/vitest#10474 (675b4)

    View changes on GitHub

v4.1.7

   🐞 Bug Fixes

• runner: Limit concurrency per task branch in addition to per leaf callbacks (backport)  -  by @​hi-ogawa in vitest-dev/vitest#10384 (4f0f2)

    View changes on GitHub

v4.1.6

   🐞 Bug Fixes

• browser: Provide project reference in ToMatchScreenshotResolvePath  -  by @​macarie and @​sheremet-va in vitest-dev/vitest#10138 (31882)
• Global sequence.concurrent: true with top-level test(..., { concurrent: false }) + depreacte sequential test API and options  -  by @​hi-ogawa, Codex and @​sheremet-va in vitest-dev/vitest#10196 (2847d)
• browser: Simplify orchestrator otel carrier  -  by @​hi-ogawa in vitest-dev/vitest#10285 (18af9)

   🏎 Performance

• Stringify diff objects only once  -  by @​sheremet-va in vitest-dev/vitest#10276 (9f7b1)

    View changes on GitHub

... (truncated)

Commits

• db616d2 chore: release v4.1.10 (#10718)
• a7a61e7 chore: release v4.1.9 (#10598)
• e61f2dd chore: release v4.1.8
• e4067b3 fix(browser): disable client cdp API when allowWrite/allowExec: false [ba...
• a09d472 chore: release v4.1.7
• a8fd24c chore: release v4.1.6
• e399846 chore: release v4.1.5
• See full diff in compare view

Updates eslint from 10.5.0 to 10.8.0

Release notes

Sourced from eslint's releases.

v10.8.0

Features

• 2fee9bb feat: export ConfigObject from eslint/config (#21082) (sethamus)

Bug Fixes

• 6b8d2f7 fix: escape reserved characters in rule id in html formatter (#21129) (Francesco Trotta)
• 9091071 fix: prevent no-unreachable-loop crash when all loop types are ignored (#21116) (Pixel)
• e23fafe fix: prefer-object-spread add semicolon when adding parenthesis (#21081) (synthex-byte)
• 20b5ad0 fix: quadratic-time regex in prefer-template (#21096) (Milos Djermanovic)
• 8b6f6c0 fix: apply ignore configs to computed methods in class-methods-use-this (#21094) (Pixel)
• b2c608c fix: NewExpression with parenthesized callee in preserve-caught-error (#21083) (Francesco Trotta)

Documentation

• 6ddf858 docs: fix broken Specify Parser Options anchor link (#21106) (Minsu)
• 784dfbe docs: Clarify no-eq-null description (#21120) (Park Harin)
• 7ec733a docs: Fix typos and grammar in glossary (#21095) (Marry (Subin Yang))
• 92bb13f docs: replace quake link (#21108) (Jung Hyeon Jun)
• 68eb4a5 docs: fix broken Specify Globals anchor links in rule pages (#21103) (Minsu)
• d28f697 docs: replace Code Climate CLI links with Qlty CLI links (#21099) (Jung Hyeon Jun)
• eccc68d docs: correct --suppressions-location option description (#21093) (Ga eun Lee)
• c5963f7 docs: Update README (GitHub Actions Bot)

Chores

• 4fbf46d test: pin webpack version to 5.108.4 (#21137) (Francesco Trotta)
• 2d063e2 chore: update HTTP URLs to HTTPS in JSDoc and comments (#21101) (Bo Hyun Kim)
• eccbe7b test: add error locations to no-class-assign (#21123) (devoil)
• e7d1e43 ci: bump actions/setup-go from 6 to 7 (#21118) (dependabot[bot])
• e9d66d0 ci: bump actions/setup-node from 6 to 7 (#21119) (dependabot[bot])
• ee225b6 test: Add error location details to no-eq-null rule (#21117) (Park Harin)
• 044a627 chore: update minimatch to ^10.2.5 (#21107) (김채영)
• fb09aa8 chore: update ecosystem plugins (#21115) (ESLint Bot)
• 5abd878 test: add error locations to no-proto (#21114) (Gihyeon Jeong / 정기현)
• 9715887 test: Add error location details to no-div-regex (#21110) (Park Harin)
• a746ec6 test: add error locations to no-new-wrappers (#21109) (Gihyeon Jeong / 정기현)
• 8dde645 test: add error locations to no-ex-assign (#21102) (devoil)
• 13ab0ec test: add error locations to no-label-var (#21098) (Gihyeon Jeong / 정기현)
• a99906f test: Add error location details to no-delete-var rule (#21105) (Park Harin)
• c47e8dc chore: add missing backticks to languages/js/index.js (#21104) (beeen)
• 0174428 chore: add missing backticks to translate-cli-options.js (#21097) (dongkyu lee)
• 3d36589 chore: add missing backticks to serialization.js (#21091) (이규환)
• dcc9312 test: add error locations to eqeqeq (#21090) (Ga eun Lee)
• 2710b18 ci: Add explicit permissions to rebuild-docs-sites workflow (#21089) (Marry (Subin Yang))
• 5d2f866 chore: update dependency prettier to v3.9.5 (#21086) (renovate[bot])
• d584e31 chore: fix failing ecosystem test for eslint-plugin-unicorn (#21084) (Francesco Trotta)
• bf3eda0 chore: update ecosystem plugins (#21079) (ESLint Bot)

v10.7.0

Features

• cf2a9bf feat: add errorClassNames option to preserve-caught-error rule (#21032) (sethamus)
• f8b873a feat: max-nested-callbacks option for constructor callbacks (#21063) (fnx)

... (truncated)

Commits

• 749dfed 10.8.0
• 4bd0d75 Build: changelog update for 10.8.0
• 4fbf46d test: pin webpack version to 5.108.4 (#21137)
• 6ddf858 docs: fix broken Specify Parser Options anchor link (#21106)
• 784dfbe docs: Clarify no-eq-null description (#21120)
• 6b8d2f7 fix: escape reserved characters in rule id in html formatter (#21129)
• 2d063e2 chore: update HTTP URLs to HTTPS in JSDoc and comments (#21101)
• eccbe7b test: add error locations to no-class-assign (#21123)
• 2fee9bb feat: export ConfigObject from eslint/config (#21082)
• e7d1e43 ci: bump actions/setup-go from 6 to 7 (#21118)
• Additional commits viewable in compare view

Updates fast-check from 3.23.2 to 4.9.0

Release notes

Sourced from fast-check's releases.

Shrinkable entityGraph and few performance chips

[Code][Diff]

Features

• (PR#7008) Towards shrinkable entityGraph thanks to chainUntil

Fixes

• (PR#7010) Bug: Fix latent state-sharing bug in entityGraph
• (PR#7063) Bug: Equiprobable alternatives in stringMatching
• (PR#6973) CI: Drop caches on push for build package flow
• (PR#6971) CI: Only mark fast-check's releases as latest
• (PR#6974) CI: Drop pull_request_target flows
• (PR#6975) CI: Drop discussion creation on release publish
• (PR#6976) CI: Drop caches from publication steps
• (PR#6977) CI: Revert "Drop...

  Description has been truncated