Skip to content

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

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/dev-dependencies-2e66246efd
Open

chore(deps-dev): bump the dev-dependencies group across 1 directory with 17 updates#132
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/dev-dependencies-2e66246efd

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 18, 2026

Copy link
Copy Markdown

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

Package From To
@arethetypeswrong/cli 0.18.4 0.18.5
@changesets/cli 2.31.0 3.0.3
@cosyte/eslint-config 0.0.3 0.0.6
@cosyte/prettier-config 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.5.1
@vitest/coverage-v8 4.1.4 5.0.1
eslint 10.5.0 10.10.0
fast-check 3.23.2 4.10.0
prettier 3.8.3 3.9.6
simple-git-hooks 2.13.0 2.14.0
tsx 4.21.0 4.23.13
typescript 5.9.3 7.0.2
vite 7.3.6 8.3.0
vitest 4.1.4 5.0.1

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

Updates @changesets/cli from 2.31.0 to 3.0.3

Release notes

Sourced from @​changesets/cli's releases.

@​changesets/cli@​3.0.3

Patch Changes

  • #2297 3f163da Thanks @​Andarist! - Fixed semver ranges (such as >=1.0.0 <2.0.0) getting cut off (>=2.0.0) when updating internal dependencies.

  • #2276 ca9d110 Thanks @​Andarist! - Fixed pnpm 10 compatibility with npm 12 when reading registry information, packing, and publishing packages.

  • Updated dependencies [3f163da, bfe9050, e522996]:

    • @​changesets/apply-release-plan@​8.1.1
    • @​changesets/config@​4.0.1

@​changesets/cli@​3.0.2

Patch Changes

@​changesets/cli@​3.0.1

Patch Changes

@​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.

... (truncated)

Changelog

Sourced from @​changesets/cli's changelog.

3.0.3

Patch Changes

  • #2297 3f163da Thanks @​Andarist! - Fixed semver ranges (such as >=1.0.0 <2.0.0) getting cut off (>=2.0.0) when updating internal dependencies.

  • #2276 ca9d110 Thanks @​Andarist! - Fixed pnpm 10 compatibility with npm 12 when reading registry information, packing, and publishing packages.

  • Updated dependencies [3f163da, bfe9050, e522996]:

    • @​changesets/apply-release-plan@​8.1.1
    • @​changesets/config@​4.0.1

3.0.2

Patch Changes

3.0.1

Patch Changes

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

... (truncated)

Commits

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.

[0.0.6] - 2026-08-04

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.

[0.0.4] - 2026-08-04

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/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.

[0.0.4] - 2026-08-04

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.

[0.0.3] - 2026-08-04

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.

[0.0.4] - 2026-08-04

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.5.1

Commits

Updates @vitest/coverage-v8 from 4.1.4 to 5.0.1

Release notes

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

v5.0.1

   🚀 Features

   🐞 Bug Fixes

    View changes on GitHub

v5.0.0

Vitest 5 is officially out! This release focuses on performance and brings a lot of new features while fixing long-standing bugs. See our blog post for the official announcement.

   🚨 Breaking Changes

... (truncated)

Commits

Updates eslint from 10.5.0 to 10.10.0

Release notes

Sourced from eslint's releases.

v10.10.0

Features

  • 264b434 feat: add d and v flags to no-unexpected-multiline (#21305) (Gihyeon Jeong / 정기현)
  • c6cc6c5 feat: check Object.prototype property names in new-cap (#21269) (crimsonjay0)
  • 5661fa6 feat: no-extra-bind false negatives with class fields and static blocks (#21260) (synthex-byte)

Bug Fixes

  • bb47dc6 fix: update dependency file-entry-cache to v11 (#20801) (Milos Djermanovic)
  • 427ac0a fix: use format strings in debug calls (#21247) (Francesco Trotta)
  • 9d81532 fix: support __proto__ in /* exported */ comments (#21261) (sethamus)
  • 87e0a08 fix: prefer-object-has-own autofix breaks when Object is shadowed (#21282) (김채영)
  • 8e2cb14 fix: new-cap false positive for UTC calls with properties: false (#21275) (Pixel)
  • 9f4a364 fix: Ignore static imports in no-unreachable (#21276) (Taha Kotil)

Documentation

  • 2417cad docs: Update README (GitHub Actions Bot)
  • 9cecb8a docs: document \c control letter escapes in no-control-regex (#21286) (한국)
  • 8724829 docs: update compat table links (#21263) (fnx)
  • 5634542 docs: Clarify eqeqeq suggestion behavior (#21256) (Müslüm Yılmaz)

Chores

  • b3d876b chore: disable npm audit in ecosystem tests (#21306) (Francesco Trotta)
  • 1696682 ci: restore EMFILE test on Node.js 26 (#21297) (Marry (Subin Yang))
  • 2c7f5d6 chore: update github/codeql-action action to v4.37.9 (#21296) (renovate[bot])
  • 3c753f1 chore: update eslint (#21289) (renovate[bot])
  • 1c73469 chore: update ecosystem plugins (#21280) (ESLint Bot)
  • 08a02be test: add error locations to no-extra-boolean-cast (#21266) (lumir)
  • 77bb1db chore: update github/codeql-action action to v4.37.8 (#21270) (renovate[bot])
  • 007e81a ci: skip EMFILE test on Node.js 26 (Description has been truncated

@dependabot
chore(deps-dev): bump the dev-dependencies group across 1 directory w…
cfc7dd9 
…ith 17 updates

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

| Package | From | To |
| --- | --- | --- |
| [@arethetypeswrong/cli](https://github.com/arethetypeswrong/arethetypeswrong.github.io/tree/HEAD/packages/cli) | `0.18.4` | `0.18.5` |
| [@changesets/cli](https://github.com/changesets/changesets/tree/HEAD/packages/cli) | `2.31.0` | `3.0.3` |
| [@cosyte/eslint-config](https://github.com/cosyte/config/tree/HEAD/packages/eslint-config) | `0.0.3` | `0.0.6` |
| [@cosyte/prettier-config](https://github.com/cosyte/config/tree/HEAD/packages/prettier-config) | `0.0.2` | `0.0.4` |
| [@cosyte/tsconfig](https://github.com/cosyte/config/tree/HEAD/packages/tsconfig) | `0.0.2` | `0.0.4` |
| [@cosyte/tsup-config](https://github.com/cosyte/config/tree/HEAD/packages/tsup-config) | `0.0.1` | `0.0.3` |
| [@cosyte/vitest-config](https://github.com/cosyte/config/tree/HEAD/packages/vitest-config) | `0.0.2` | `0.0.4` |
| [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) | `22.20.0` | `26.5.1` |
| [@vitest/coverage-v8](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8) | `4.1.4` | `5.0.1` |
| [eslint](https://github.com/eslint/eslint) | `10.5.0` | `10.10.0` |
| [fast-check](https://github.com/dubzzz/fast-check/tree/HEAD/packages/fast-check) | `3.23.2` | `4.10.0` |
| [prettier](https://github.com/prettier/prettier) | `3.8.3` | `3.9.6` |
| [simple-git-hooks](https://github.com/toplenboren/simple-git-hooks) | `2.13.0` | `2.14.0` |
| [tsx](https://github.com/privatenumber/tsx) | `4.21.0` | `4.23.13` |
| [typescript](https://github.com/microsoft/TypeScript) | `5.9.3` | `7.0.2` |
| [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) | `7.3.6` | `8.3.0` |
| [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) | `4.1.4` | `5.0.1` |



Updates `@arethetypeswrong/cli` from 0.18.4 to 0.18.5
- [Release notes](https://github.com/arethetypeswrong/arethetypeswrong.github.io/releases)
- [Changelog](https://github.com/arethetypeswrong/arethetypeswrong.github.io/blob/main/packages/cli/CHANGELOG.md)
- [Commits](https://github.com/arethetypeswrong/arethetypeswrong.github.io/commits/HEAD/packages/cli)

Updates `@changesets/cli` from 2.31.0 to 3.0.3
- [Release notes](https://github.com/changesets/changesets/releases)
- [Changelog](https://github.com/changesets/changesets/blob/main/packages/cli/CHANGELOG.md)
- [Commits](https://github.com/changesets/changesets/commits/@changesets/cli@3.0.3/packages/cli)

Updates `@cosyte/eslint-config` from 0.0.3 to 0.0.6
- [Release notes](https://github.com/cosyte/config/releases)
- [Changelog](https://github.com/cosyte/config/blob/main/packages/eslint-config/CHANGELOG.md)
- [Commits](https://github.com/cosyte/config/commits/@cosyte/eslint-config@0.0.6/packages/eslint-config)

Updates `@cosyte/prettier-config` from 0.0.2 to 0.0.4
- [Release notes](https://github.com/cosyte/config/releases)
- [Changelog](https://github.com/cosyte/config/blob/main/packages/prettier-config/CHANGELOG.md)
- [Commits](https://github.com/cosyte/config/commits/@cosyte/prettier-config@0.0.4/packages/prettier-config)

Updates `@cosyte/tsconfig` from 0.0.2 to 0.0.4
- [Release notes](https://github.com/cosyte/config/releases)
- [Changelog](https://github.com/cosyte/config/blob/main/packages/tsconfig/CHANGELOG.md)
- [Commits](https://github.com/cosyte/config/commits/@cosyte/tsconfig@0.0.4/packages/tsconfig)

Updates `@cosyte/tsup-config` from 0.0.1 to 0.0.3
- [Release notes](https://github.com/cosyte/config/releases)
- [Changelog](https://github.com/cosyte/config/blob/main/packages/tsup-config/CHANGELOG.md)
- [Commits](https://github.com/cosyte/config/commits/@cosyte/tsup-config@0.0.3/packages/tsup-config)

Updates `@cosyte/vitest-config` from 0.0.2 to 0.0.4
- [Release notes](https://github.com/cosyte/config/releases)
- [Changelog](https://github.com/cosyte/config/blob/main/packages/vitest-config/CHANGELOG.md)
- [Commits](https://github.com/cosyte/config/commits/@cosyte/vitest-config@0.0.4/packages/vitest-config)

Updates `@types/node` from 22.20.0 to 26.5.1
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node)

Updates `@vitest/coverage-v8` from 4.1.4 to 5.0.1
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md)
- [Commits](https://github.com/vitest-dev/vitest/commits/v5.0.1/packages/coverage-v8)

Updates `eslint` from 10.5.0 to 10.10.0
- [Release notes](https://github.com/eslint/eslint/releases)
- [Commits](eslint/eslint@v10.5.0...v10.10.0)

Updates `fast-check` from 3.23.2 to 4.10.0
- [Release notes](https://github.com/dubzzz/fast-check/releases)
- [Changelog](https://github.com/dubzzz/fast-check/blob/main/packages/fast-check/CHANGELOG.md)
- [Commits](https://github.com/dubzzz/fast-check/commits/v4.10.0/packages/fast-check)

Updates `prettier` from 3.8.3 to 3.9.6
- [Release notes](https://github.com/prettier/prettier/releases)
- [Changelog](https://github.com/prettier/prettier/blob/main/CHANGELOG.md)
- [Commits](prettier/prettier@3.8.3...3.9.6)

Updates `simple-git-hooks` from 2.13.0 to 2.14.0
- [Release notes](https://github.com/toplenboren/simple-git-hooks/releases)
- [Changelog](https://github.com/toplenboren/simple-git-hooks/blob/master/CHANGELOG.md)
- [Commits](toplenboren/simple-git-hooks@2.13.0...2.14.0)

Updates `tsx` from 4.21.0 to 4.23.13
- [Release notes](https://github.com/privatenumber/tsx/releases)
- [Changelog](https://github.com/privatenumber/tsx/blob/master/release.config.cjs)
- [Commits](privatenumber/tsx@v4.21.0...v4.23.13)

Updates `typescript` from 5.9.3 to 7.0.2
- [Release notes](https://github.com/microsoft/TypeScript/releases)
- [Commits](microsoft/TypeScript@v5.9.3...v7.0.2)

Updates `vite` from 7.3.6 to 8.3.0
- [Release notes](https://github.com/vitejs/vite/releases)
- [Changelog](https://github.com/vitejs/vite/blob/main/packages/vite/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite/commits/create-vite@8.3.0/packages/vite)

Updates `vitest` from 4.1.4 to 5.0.1
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md)
- [Commits](https://github.com/vitest-dev/vitest/commits/v5.0.1/packages/vitest)

---
updated-dependencies:
- dependency-name: "@arethetypeswrong/cli"
  dependency-version: 0.18.5
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dev-dependencies
- dependency-name: "@changesets/cli"
  dependency-version: 3.0.3
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: dev-dependencies
- dependency-name: "@cosyte/eslint-config"
  dependency-version: 0.0.6
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dev-dependencies
- dependency-name: "@cosyte/prettier-config"
  dependency-version: 0.0.4
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dev-dependencies
- dependency-name: "@cosyte/tsconfig"
  dependency-version: 0.0.4
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dev-dependencies
- dependency-name: "@cosyte/tsup-config"
  dependency-version: 0.0.3
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dev-dependencies
- dependency-name: "@cosyte/vitest-config"
  dependency-version: 0.0.4
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dev-dependencies
- dependency-name: "@types/node"
  dependency-version: 26.5.1
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: dev-dependencies
- dependency-name: "@vitest/coverage-v8"
  dependency-version: 5.0.1
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: dev-dependencies
- dependency-name: eslint
  dependency-version: 10.10.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dev-dependencies
- dependency-name: fast-check
  dependency-version: 4.10.0
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: dev-dependencies
- dependency-name: prettier
  dependency-version: 3.9.6
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dev-dependencies
- dependency-name: simple-git-hooks
  dependency-version: 2.14.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dev-dependencies
- dependency-name: tsx
  dependency-version: 4.23.13
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dev-dependencies
- dependency-name: typescript
  dependency-version: 7.0.2
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: dev-dependencies
- dependency-name: vite
  dependency-version: 8.3.0
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: dev-dependencies
- dependency-name: vitest
  dependency-version: 5.0.1
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: dev-dependencies
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Sep 18, 2026
@dependabot
dependabot Bot requested a review from NSchatz as a code owner September 18, 2026 09:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@NSchatz NSchatz Awaiting requested review from NSchatz NSchatz is a code owner

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants