chore(deps-dev): bump the npm-development group across 1 directory with 12 updates

[dependabot]

Bumps the npm-development group with 12 updates in the / directory:

Package	From	To
@eslint/compat	1.3.2	1.4.0
@pixpilot/dev-config	3.1.0	3.1.2
@pixpilot/eslint-config	2.7.0	2.8.0
@types/node	24.3.0	24.7.0
@typescript-eslint/eslint-plugin	8.39.1	8.45.0
@typescript-eslint/parser	8.39.1	8.45.0
cross-env	10.0.0	10.1.0
esbuild	0.19.12	0.25.10
eslint	9.33.0	9.37.0
lint-staged	16.1.5	16.2.3
tsx	4.20.4	4.20.6
typescript	5.9.2	5.9.3

Updates @eslint/compat from 1.3.2 to 1.4.0

Release notes

Sourced from @​eslint/compat's releases.

migrate-config: v1.4.0

1.4.0 (2025-03-14)

Features

• Use defineConfig() and globalIgnores() helpers (#164) (727ec5d)

compat: v1.4.0

1.4.0 (2025-09-16)

Features

• Add config types in @​eslint/core (#237) (7b6dd37)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @​eslint/core bumped from ^0.15.2 to ^0.16.0

migrate-config: v1.3.8

1.3.8 (2025-02-21)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @​eslint/compat bumped from ^1.2.6 to ^1.2.7

migrate-config: v1.3.7

1.3.7 (2025-01-31)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @​eslint/compat bumped from ^1.2.5 to ^1.2.6

migrate-config: v1.3.6

1.3.6 (2025-01-09)

Dependencies

• The following workspace dependencies were updated

... (truncated)

Changelog

Sourced from @​eslint/compat's changelog.

1.4.0 (2025-09-16)

Features

• Add config types in @​eslint/core (#237) (7b6dd37)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • @​eslint/core bumped from ^0.15.2 to ^0.16.0

Commits

• 7f592e3 chore: release main (#257)
• 4f07e51 docs: correct bun installation command and use defineConfig in README (#269)
• ab10682 docs: Update README sponsors
• 7255100 chore: standardize test filenames to *.test.js (#267)
• 7e61e90 test: remove deprecated type property (#266)
• 100a4c7 docs: Update README sponsors
• b23f179 docs: Update README sponsors
• 7b6dd37 feat: Add config types in @​eslint/core (#237)
• 8ba766a refactor: update eslint-config-eslint (#253)
• 62089bc docs: Update README sponsors
• Additional commits viewable in compare view

Updates @pixpilot/dev-config from 3.1.0 to 3.1.2

Release notes

Sourced from @​pixpilot/dev-config's releases.

v3.1.2

v3.1.2

Patch Changes

• update file patterns in overrides for JSON files

v3.1.1

v3.1.1

Patch Changes

• format overrides array for consistency
• add additional file types to overrides

Changelog

Sourced from @​pixpilot/dev-config's changelog.

3.1.2

Patch Changes

• update file patterns in overrides for JSON files

3.1.1

Patch Changes

• format overrides array for consistency
• add additional file types to overrides

Commits

• cf3b717 chore(release): 3.1.2 [skip ci]
• 56418fe Merge branch 'main' of https://github.com/pixpilot/dev-config
• 8f2cc94 fix(prettier): update file patterns in overrides for JSON files
• c54134c chore(release): 3.1.1 [skip ci]
• 7d82b3b fix(prettier): format overrides array for consistency
• aaff48f fix(codeql): update workflow name format
• b879662 fix(prettier): add additional file types to overrides
• 7818a62 chore(codeql): update CodeQL configuration and workflow
• See full diff in compare view

Updates @pixpilot/eslint-config from 2.7.0 to 2.8.0

Commits

• See full diff in compare view

Updates @types/node from 24.3.0 to 24.7.0

Commits

• See full diff in compare view

Updates @typescript-eslint/eslint-plugin from 8.39.1 to 8.45.0

Release notes

Sourced from @​typescript-eslint/eslint-plugin's releases.

v8.45.0

8.45.0 (2025-09-29)

🚀 Features

• eslint-plugin: expose rule name via RuleModule interface (#11616)

🩹 Fixes

• disable generating declaration maps (#11627)
• ast-spec: narrow ArrowFunctionExpression.generator to false (#11636)
• eslint-plugin: [no-base-to-string] check if superclass is ignored (#11617)
• eslint-plugin: [prefer-nullish-coalescing] ignoreBooleanCoercion should not apply to top-level ternary expressions (#11614)

❤️ Thank You

• Bjorn Lu
• Josh Goldberg ✨
• mdm317
• Moses Odutusin @​thebolarin
• Yukihiro Hasegawa @​y-hsgw

You can read about our versioning strategy and releases on our website.

v8.44.1

8.44.1 (2025-09-22)

🩹 Fixes

• eslint-plugin: [no-base-to-string] make ignoredTypeNames match type names without generics (#11597)
• eslint-plugin: [no-unsafe-enum-comparison] support unions of literals (#11599)
• eslint-plugin: [await-thenable] should not report passing values to promise aggregators which may be a promise in an array literal (#11611)
• typescript-estree: forbid class property with name constructor (#11590)

❤️ Thank You

• fisker Cheung @​fisker
• Kirk Waiblinger @​kirkwaiblinger
• mdm317
• Ronen Amiel

You can read about our versioning strategy and releases on our website.

v8.44.0

8.44.0 (2025-09-15)

🚀 Features

• eslint-plugin: [await-thenable] report invalid (non-promise) values passed to promise aggregator methods (#11267)

... (truncated)

Changelog

Sourced from @​typescript-eslint/eslint-plugin's changelog.

8.45.0 (2025-09-29)

🚀 Features

• eslint-plugin: expose rule name via RuleModule interface (#11616)

🩹 Fixes

• eslint-plugin: [prefer-nullish-coalescing] ignoreBooleanCoercion should not apply to top-level ternary expressions (#11614)
• eslint-plugin: [no-base-to-string] check if superclass is ignored (#11617)

❤️ Thank You

• mdm317
• Moses Odutusin @​thebolarin
• Yukihiro Hasegawa @​y-hsgw

You can read about our versioning strategy and releases on our website.

8.44.1 (2025-09-22)

🩹 Fixes

• eslint-plugin: [await-thenable] should not report passing values to promise aggregators which may be a promise in an array literal (#11611)
• eslint-plugin: [no-unsafe-enum-comparison] support unions of literals (#11599)
• eslint-plugin: [no-base-to-string] make ignoredTypeNames match type names without generics (#11597)

❤️ Thank You

• Kirk Waiblinger @​kirkwaiblinger
• mdm317
• Ronen Amiel

You can read about our versioning strategy and releases on our website.

8.44.0 (2025-09-15)

🚀 Features

• eslint-plugin: [await-thenable] report invalid (non-promise) values passed to promise aggregator methods (#11267)

🩹 Fixes

• eslint-plugin: [no-unnecessary-type-conversion] ignore enum members (#11490)

❤️ Thank You

• Moses Odutusin @​thebolarin
• Ronen Amiel

... (truncated)

Commits

• 255e9e2 chore(release): publish 8.45.0
• 967764e fix(eslint-plugin): [prefer-nullish-coalescing] ignoreBooleanCoercion should ...
• f2eeb9d feat(eslint-plugin): expose rule name via RuleModule interface (#11616)
• 590fac6 fix(eslint-plugin): [no-base-to-string] check if superclass is ignored (#11617)
• c198052 chore(release): publish 8.44.1
• c392a0d fix(eslint-plugin): [await-thenable] should not report passing values to prom...
• 20c3d97 fix(eslint-plugin): [no-unsafe-enum-comparison] support unions of literals (#...
• 4fde781 fix(eslint-plugin): [no-base-to-string] make ignoredTypeNames match type name...
• 77056f7 chore(release): publish 8.44.0
• 684e63f chore(deps): update eslint monorepo to v9.35.0 (#11600)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for @​typescript-eslint/eslint-plugin since your current version.

Updates @typescript-eslint/parser from 8.39.1 to 8.45.0

Release notes

Sourced from @​typescript-eslint/parser's releases.

v8.45.0

8.45.0 (2025-09-29)

🚀 Features

• eslint-plugin: expose rule name via RuleModule interface (#11616)

🩹 Fixes

• disable generating declaration maps (#11627)
• ast-spec: narrow ArrowFunctionExpression.generator to false (#11636)
• eslint-plugin: [no-base-to-string] check if superclass is ignored (#11617)
• eslint-plugin: [prefer-nullish-coalescing] ignoreBooleanCoercion should not apply to top-level ternary expressions (#11614)

❤️ Thank You

• Bjorn Lu
• Josh Goldberg ✨
• mdm317
• Moses Odutusin @​thebolarin
• Yukihiro Hasegawa @​y-hsgw

You can read about our versioning strategy and releases on our website.

v8.44.1

8.44.1 (2025-09-22)

🩹 Fixes

• eslint-plugin: [no-base-to-string] make ignoredTypeNames match type names without generics (#11597)
• eslint-plugin: [no-unsafe-enum-comparison] support unions of literals (#11599)
• eslint-plugin: [await-thenable] should not report passing values to promise aggregators which may be a promise in an array literal (#11611)
• typescript-estree: forbid class property with name constructor (#11590)

❤️ Thank You

• fisker Cheung @​fisker
• Kirk Waiblinger @​kirkwaiblinger
• mdm317
• Ronen Amiel

You can read about our versioning strategy and releases on our website.

v8.44.0

8.44.0 (2025-09-15)

🚀 Features

• eslint-plugin: [await-thenable] report invalid (non-promise) values passed to promise aggregator methods (#11267)

... (truncated)

Changelog

Sourced from @​typescript-eslint/parser's changelog.

8.45.0 (2025-09-29)

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

8.44.1 (2025-09-22)

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

8.44.0 (2025-09-15)

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

8.43.0 (2025-09-08)

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

8.42.0 (2025-09-02)

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

8.41.0 (2025-08-25)

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

8.40.0 (2025-08-18)

This was a version bump only for parser to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

Commits

• 255e9e2 chore(release): publish 8.45.0
• c198052 chore(release): publish 8.44.1
• 77056f7 chore(release): publish 8.44.0
• ef9173c chore(release): publish 8.43.0
• d135909 chore(release): publish 8.42.0
• 31a7336 chore(release): publish 8.41.0
• 60c3b26 chore(release): publish 8.40.0
• See full diff in compare view

Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for @​typescript-eslint/parser since your current version.

Updates cross-env from 10.0.0 to 10.1.0

Release notes

Sourced from cross-env's releases.

v10.1.0

10.1.0 (2025-09-29)

Features

• add support for default value syntax (152ae6a)

For example:

"dev:server": "cross-env wrangler dev --port ${PORT:-8787}",

If PORT is already set, use that value, otherwise fallback to 8787.

Learn more about Shell Parameter Expansion

Commits

• 152ae6a feat: add support ofr default value syntax
• bd70d1a chore: upgrade zshy
• 8e0b190 chore(ci): get coverage
• See full diff in compare view

Updates esbuild from 0.19.12 to 0.25.10

Release notes

Sourced from esbuild's releases.

v0.25.10

• Fix a panic in a minification edge case (#4287)

  This release fixes a panic due to a null pointer that could happen when esbuild inlines a doubly-nested identity function and the final result is empty. It was fixed by emitting the value undefined in this case, which avoids the panic. This case must be rare since it hasn't come up until now. Here is an example of code that previously triggered the panic (which only happened when minifying):

  function identity(x) { return x }
  identity({ y: identity(123) })

• Fix @supports nested inside pseudo-element (#4265)

  When transforming nested CSS to non-nested CSS, esbuild is supposed to filter out pseudo-elements such as ::placeholder for correctness. The CSS nesting specification says the following:

  The nesting selector cannot represent pseudo-elements (identical to the behavior of the ':is()' pseudo-class). We’d like to relax this restriction, but need to do so simultaneously for both ':is()' and '&', since they’re intentionally built on the same underlying mechanisms.

  However, it seems like this behavior is different for nested at-rules such as @supports, which do work with pseudo-elements. So this release modifies esbuild's behavior to now take that into account:

  /* Original code */
  ::placeholder {
    color: red;
    body & { color: green }
    @supports (color: blue) { color: blue }
  }
  /* Old output (with --supported:nesting=false) */
  ::placeholder {
  color: red;
  }
  body :is() {
  color: green;
  }
  @​supports (color: blue) {
  {
  color: blue;
  }
  }
  /* New output (with --supported:nesting=false) */
  ::placeholder {
  color: red;
  }
  body :is() {
  color: green;
  }
  @​supports (color: blue) {
  ::placeholder {
  color: blue;
  }

... (truncated)

Changelog

Sourced from esbuild's changelog.

Changelog: 2024

This changelog documents all esbuild versions published in the year 2024 (versions 0.19.12 through 0.24.2).

0.24.2

• Fix regression with --define and import.meta (#4010, #4012, #4013)

  The previous change in version 0.24.1 to use a more expression-like parser for define values to allow quoted property names introduced a regression that removed the ability to use --define:import.meta=.... Even though import is normally a keyword that can't be used as an identifier, ES modules special-case the import.meta expression to behave like an identifier anyway. This change fixes the regression.

  This fix was contributed by @​sapphi-red.

0.24.1

• Allow es2024 as a target in tsconfig.json (#4004)

  TypeScript recently added es2024 as a compilation target, so esbuild now supports this in the target field of tsconfig.json files, such as in the following configuration file:

  {
    "compilerOptions": {
      "target": "ES2024"
    }
  }

  As a reminder, the only thing that esbuild uses this field for is determining whether or not to use legacy TypeScript behavior for class fields. You can read more in the documentation.

  This fix was contributed by @​billyjanitsch.

• Allow automatic semicolon insertion after get/set

  This change fixes a grammar bug in the parser that incorrectly treated the following code as a syntax error:

  class Foo {
    get
    *x() {}
    set
    *y() {}
  }

  The above code will be considered valid starting with this release. This change to esbuild follows a similar change to TypeScript which will allow this syntax starting with TypeScript 5.7.

• Allow quoted property names in --define and --pure (#4008)

  The define and pure API options now accept identifier expressions containing quoted property names. Previously all identifiers in the identifier expression had to be bare identifiers. This change now makes --define and --pure consistent with --global-name, which already supported quoted property names. For example, the following is now possible:

... (truncated)

Commits

• d6b668f publish 0.25.10 to npm
• 5088c19 refactor: use strings.Builder (#4290)
• 755da31 run make update-compat-table
• a1d9c86 fix #4287: marked the wrong issue as fixed
• 73a0b2a fix #4286: minifier panic due to identity function
• 134dadf fix #4265: @supports nested inside ::pseudo
• 195e05c publish 0.25.9 to npm
• 3dac33f fix #3131, fix #3663: yarnpnp + windows + D drive
• 0f2c5c8 mock fs now supports multiple volumes on windows
• 100a51e split out yarnpnp snapshot tests
• Additional commits viewable in compare view

Updates eslint from 9.33.0 to 9.37.0

Release notes

Sourced from eslint's releases.

v9.37.0

Features

• 39f7fb4 feat: preserve-caught-error should recognize all static "cause" keys (#20163) (Pixel998)
• f81eabc feat: support TS syntax in no-restricted-imports (#19562) (Nitin Kumar)

Bug Fixes

• a129cce fix: correct no-loss-of-precision false positives for leading zeros (#20164) (Francesco Trotta)
• 09e04fc fix: add missing AST token types (#20172) (Pixel998)
• 861c6da fix: correct ESLint typings (#20122) (Pixel998)

Documentation

• b950359 docs: fix typos across the docs (#20182) (루밀LuMir)
• 42498a2 docs: improve ToC accessibility by hiding non-semantic character (#20181) (Percy Ma)
• 29ea092 docs: Update README (GitHub Actions Bot)
• 5c97a04 docs: show availableUntil in deprecated rule banner (#20170) (Pixel998)
• 90a71bf docs: update README files to add badge and instructions (#20115) (루밀LuMir)
• 1603ae1 docs: update references from master to main (#20153) (루밀LuMir)

Chores

• afe8a13 chore: update @eslint/js dependency to version 9.37.0 (#20183) (Francesco Trotta)
• abee4ca chore: package.json update for @​eslint/js release (Jenkins)
• fc9381f chore: fix typos in comments (#20175) (overlookmotel)
• e1574a2 chore: unpin jiti (#20173) (renovate[bot])
• e1ac05e refactor: mark ESLint.findConfigFile() as async, add missing docs (#20157) (Pixel998)
• 347906d chore: update eslint (#20149) (renovate[bot])
• 0cb5897 test: remove tmp dir created for circular fixes in multithread mode test (#20146) (Milos Djermanovic)
• bb99566 ci: pin jiti to version 2.5.1 (#20151) (Pixel998)
• 177f669 perf: improve worker count calculation for "auto" concurrency (#20067) (Francesco Trotta)
• 448b57b chore: Mark deprecated formatting rules as available until v11.0.0 (#20144) (Milos Djermanovic)

v9.36.0

Features

• 47afcf6 feat: correct preserve-caught-error edge cases (#20109) (Francesco Trotta)

Bug Fixes

• 75b74d8 fix: add missing rule option types (#20127) (ntnyq)
• 1c0d850 fix: update eslint-all.js to use Object.freeze for rules object (#20116) (루밀LuMir)
• 7d61b7f fix: add missing scope types to Scope.type (#20110) (Pixel998)
• 7a670c3 fix: correct rule option typings in rules.d.ts (#20084) (Pixel998)

Documentation

• b73ab12 docs: update examples to use defineConfig (#20131) (sethamus)
• 31d9392 docs: fix typos (#20118) (Pixel998)
• c7f861b docs: Update README (GitHub Actions Bot)
• 6b0c08b docs: Update README (GitHub Actions Bot)
• 91f97c5 docs: Update README (GitHub Actions Bot)

Chores

• 12411e8 chore: upgrade @​eslint/js@​9.36.0 (#20139) (Milos Djermanovic)
• 488cba6 chore: package.json update for @​eslint/js release (Jenkins)

... (truncated)

Commits

• d5d1bdf 9.37.0
• 94865ff Build: changelog update for 9.37.0
• afe8a13 chore: update @eslint/js dependency to version 9.37.0 (#20183)
• abee4ca chore: package.json update for @​eslint/js release
• b950359 docs: fix typos across the docs (#20182)
• 42498a2 docs: improve ToC accessibility by hiding non-semantic character (#20181)
• fc9381f chore: fix typos in comments (#20175)
• e1574a2 chore: unpin jiti (#20173)
• 29ea092 docs: Update README
• a129cce fix: correct no-loss-of-precision false positives for leading zeros (#20164)
• Additional commits viewable in compare view

Updates lint-staged from 16.1.5 to 16.2.3

Release notes

Sourced from lint-staged's releases.

v16.2.3

Patch Changes

• #1669 27cd541 Thanks @​iiroj! - When using --fail-on-changes, automatically hidden (partially) unstaged changes are no longer counted to make lint-staged fail.

v16.2.2

Patch Changes

• #1667 699f95d Thanks @​iiroj! - The backup stash will not be dropped when using --fail-on-changes and there are errors. When reverting to original state is disabled (via --no-revert or --fail-on-changes), hidden (partially) unstaged changes are still restored automatically so that it's easier to resolve the situation manually.

  Additionally, the example for using the backup stash manually now uses the correct backup hash, if available:

  % npx lint-staged --fail-on-changes
  ✔ Backed up original state in git stash (c18d55a3)
  ✔ Running tasks for staged files...
  ✖ Tasks modified files and --fail-on-changes was used!
  ↓ Cleaning up temporary files...
  ✖ lint-staged failed because --fail-on-changes was used.
  Any lost modifications can be restored from a git stash:
  > git stash list --format="%h %s"
  c18d55a3 On main: lint-staged automatic backup
  > git apply --index c18d55a3

v16.2.1

Patch Changes

• #1664 8277b3b Thanks @​iiroj! - The built-in TypeScript types have been updated to more closely match the implementation. Notably, the list of staged files supplied to task functions is readonly string[] and can't be mutated. Thanks @​outslept!

  export default {
  ---  "*": (files: string[]) => void console.log('staged files', files)
  +++  "*": (files: readonly string[]) => void console.log('staged files', files)
  }

• #1654 70b9af3 Thanks @​iiroj! - This version has been published from GitHub Actions using Trusted Publishing for npm packages.

• #1659 4996817 Thanks @​iiroj! - Fix searching configuration files when the working directory is a subdirectory of a git repository, and there are package.json files in the working directory. This situation might happen when running lint-staged for a single package in a monorepo.

• #1654 7021f0a Thanks @​iiroj! - Return the caret semver range (^) to direct dependencies so that future patch and minor versions are allowed. This enables projects to better maintain and deduplicate their own transitive dependencies while not requiring direct updates to lint-staged. This was changed in 16.2.0 after the vulnerability issues with chalk and debug, which were also removed in the same version.

  Given the recent vulnerabilities in the npm ecosystem, it's best to be very careful when updating dependencies.

v16.2.0

Minor Changes

... (truncated)

Changelog

Sourced from lint-staged's changelog.

16.2.3

Patch Changes

• #1669 27cd541 Thanks @​iiroj! - When using --fail-on-changes, automatically hidden (partially) unstaged changes are no longer counted to make lint-staged fail.

16.2.2

Patch Changes

• #1667 699f95d Thanks @​iiroj! - The backup stash will not be dropped when using --fail-on-changes and there are errors. When reverting to original state is disabled (via --no-revert or --fail-on-changes), hidden (partially) unstaged changes are still restored automatically so that it's easier to resolve the situation manually.

  Additionally, the example for using the backup stash manually now uses the correct backup hash, if available:

  % npx lint-staged --fail-on-changes
  ✔ Backed up original state in git stash (c18d55a3)
  ✔ Running tasks for staged files...
  ✖ Tasks modified files and --fail-on-changes was used!
  ↓ Cleaning up temporary files...
  ✖ lint-staged failed because --fail-on-changes was used.
  Any lost modifications can be restored from a git stash:
  > git stash list --format="%h %s"
  c18d55a3 On main: lint-staged automatic backup
  > git apply --index c18d55a3

16.2.1

Patch Changes

• #1664 8277b3b Thanks @​iiroj! - The built-in TypeScript types have been updated to more closely match the implementation. Notably, the list of staged files supplied to task functions is readonly string[] and can't be mutated. Thanks @​outslept!

  export default {
  ---  "*": (files: string[]) => void console.log('staged files', files)
  +++  "*": (files: readonly string[]) => void console.log('staged files', files)
  }

• #1654 70b9af3 Thanks @​iiroj! - This version has been published from GitHub Actions using Trusted Publishing for npm packages.

• #1659 4996817 Thanks @​iiroj! - Fix searching configuration files when the working directory is a subdirectory of a git repository, and there are package.json files in the working directory. This situation might happen when running lint-staged for a single package in a monorepo.

• #1654 7021f0a Thanks @​iiroj! - Return the caret semver range (^) to direct dependencies so that future patch and minor versions are allowed. This enables projects to better maintain and deduplicate their own transitive dependencies while not requiring direct updates to lint-staged. This was changed in 16.2.0 after the vulnerability issues with chalk and debug, which were also removed in the same version.

  Given the recent vulnerabilities in the npm ecosystem, it's best to be very careful when updating dependencies.

... (truncated)

Commits

• bdcd03a chore(changeset): release
• 27cd541 fix: do not count hidden (partially) unstaged changes when using `--fail-on-c...
• ab2f42e fix: emit correct value to debug logs
• 3fc5832 refactor: make general error messages more clear they originate from lint-staged
• 409d79a chore(changeset): release
• 7edaee9 docs: fix typo in changeset
• 699f95d fix: backup stash example uses real hash if available
• 47d01a9 fix: print backup stash example when failing to --fail-on-changes
• 325dc03 fix: restore unstaged changes on errors when --fail-on-errors or `--no-reve...
• 53bb27b fix: do not drop backup stash when errors and --fail-on-changes was used
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for lint-staged since your current version.

Updates tsx from 4.20.4 to 4.20.6

Release notes

Sourced from tsx's releases.

v4.20.6

4.20.6 (2025-09-26)

Bug Fixes

• properly hide relaySignal from process.listeners() (#741) (710a424)

---

This release is also available on:

• npm package (@​latest dist-tag)

v4.20.5

4.20.5 (2025-08-24)

Bug Fixes

• handle ambiguous packages (796053a)

---

This release is also available on:

• npm package (@​latest dist-tag)

Commits

• 710a424 fix: properly hide relaySignal from process.listeners() (#741)
• 20b91c4 docs: make sponsors dynamic
• 08dcd59 chore: move vercel settings to root
• e6d1a47 docs: obfuscate aside classname
• de2719d style: remove unused variable
• 13f2954 chore: upgrade docs deps
• 0504525 chore: upgrade manten
• 132fdd8 test: assert require.cache
• f057e7d test: require loop
• a6f8f9f refactor: getFormat to handle all formats
• Additional commits viewable in compare view

Updates typescript from 5.9.2 to 5.9.3

Release notes

Sourced from typescript's releases.

TypeScript 5.9.3

Note: this tag was recreated to point at the correct commit. The npm package contained the correct content.

For release notes, check out the release announcement

• fixed issues query for Typescript 5.9.0 (Beta).
• fixed issues query for Typescript 5.9.1 (RC)...

  Description has been truncated

[dependabot]

Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting @dependabot recreate.

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.