[dependabot]

Bumps the dev-dependencies group with 8 updates:

Package	From	To
@types/mocha	9.0.0	10.0.10
@types/node	16.4.14	26.6.6
husky	7.0.4	9.1.7
lint-staged	11.1.4	17.6.0
sinon	11.1.2	22.1.0
@types/sinon	10.0.20	22.0.2
ts-node	10.1.0	10.9.2
typescript	4.3.5	7.0.2

Updates @types/mocha from 9.0.0 to 10.0.10

Commits

• See full diff in compare view

Updates @types/node from 16.4.14 to 26.6.6

Commits

• See full diff in compare view

Updates husky from 7.0.4 to 9.1.7

Release notes

Sourced from husky's releases.

v9.1.7

What's Changed

• fix: add husky label to deprecated warning by @​smackfu in typicode/husky#1538

New Contributors

• @​smackfu made their first contribution in typicode/husky#1538

Full Changelog: typicode/husky@v9.1.6...v9.1.7

v9.1.6

What's Changed

• Fix issue where example pre-commit file is generated incorrectly by @​dexmlee in typicode/husky#1519

New Contributors

• @​OlegKipchatov made their first contribution in typicode/husky#1495
• @​Byron2016 made their first contribution in typicode/husky#1499
• @​dexmlee made their first contribution in typicode/husky#1519

Full Changelog: typicode/husky@v9.1.5...v9.1.6

v9.1.5

What's Changed

• fixes #1494, support pre-merge-commit hook by @​RainMeoCat in typicode/husky#1497

New Contributors

• @​RainMeoCat made their first contribution in typicode/husky#1497

Full Changelog: typicode/husky@v9.1.4...v9.1.5

v9.1.4

• Improve deprecation notice

v9.1.3

• fix: better handle space in PATH

v9.1.2

Show a message instead of automatically removing deprecated code.

This only concerns projects that still have the following code in their hooks:

- #!/usr/bin/env sh # <- This is deprecated, remove it
- . "$(dirname -- "$0")/_/husky.sh"  # <- This is deprecated, remove it
Rest of your hook code

Hooks with these lines will fail in v10.0.0

v9.1.1

... (truncated)

Commits

• 799e84b 9.1.7
• 30f2049 fix: add husky label to deprecated warning (#1538)
• a2d942a 9.1.6
• b4465ed fix: add parens around the null coalescing operator to fix issues when npm_co...
• 3b3e7f1 docs(spanish): improve spanish translation (#1504)
• dcf3aed dosc: repair support Spanish sponsors links (#1500)
• c3afd5f docs: support Spanish documentation (#1499)
• c5f4f48 docs: support Russian documentation (#1495)
• 2fee8d2 9.1.5
• 397e7f0 fixes #1494 support pre-merge-commit hook
• Additional commits viewable in compare view

Updates lint-staged from 11.1.4 to 17.6.0

Release notes

Sourced from lint-staged's releases.

v17.6.0

Minor Changes

• #1850 938d3f4 - Task functions like { title, task } can now use a logger function log() to emit output while the task runs. By default, the output will only be visible if the task fails, unless the --verbose option was used. Additionally, when the task rejects, the error will be shown in the output.

  import { defineConfig } from 'lint-staged/config'
  export default defineConfig({
  '*': {
  title: 'Fail if PDF files are committed',
  task: async (filepaths, { log }) => {
  const pdfFiles = filepaths.filter((f) => f.toLowerCase().endsWith('.pdf'))
  if (pdfFiles.length > 0) {
  log('PDF files should not be committed: %s', pdfFiles)
  throw new Error('Failed')
  }
  },
  },
  })

• #1854 30562bc - lint-staged now stages changes to all tracked files modified by tasks, including files that weren’t originally staged or didn’t match the configured globs. This can happen when your task has side-effects, or it's a function that ignores the staged files like () => "prettier --write .".

  If you have unstaged changes in a file and the task also edits that file, your unstaged changes will be staged too. Use --hide-unstaged to hide your changes while tasks run.

Patch Changes

• #1860 4296532 - The assignment of staged files to lint-staged configuration files (when using multiple, for example in a monorepo) has been rewritten to be more efficient. As a reminder, each staged file is assigned to exactly one configuration (the closest one), even if that config doesn't match the file in its globs.

• #1861 c45f28a - Fix running parallel tasks for a single glob, when tasks are created by a function. Nesting one level of arrays inside an array of tasks will result in the inner tasks running in parallel. This behavior should now be consistent when creating tasks using functions. In the following example eslint and prettier will run in parallel (for all files, when any JS files are staged):

  import { defineConfig } from 'lint-staged/config'
  export default defineConfig({
  '*.js': () => [['eslint --max-warnings=0 .', 'prettier --list-different .']],
  })

• #1859 f0ea69d - Various performance improvements from skipping redundant internal Git calls.

• #1856 69d7d17 - Partially staged changes are hidden in a uniquely-named patch file to avoid multiple invocations of lint-staged overwriting it. This makes it safer to run lint-staged in multiple worktrees at the same time.

v17.5.1

Patch Changes

• #1852 bfcca94 - Fix TypeScript issue TS1254 from defineConfig() by changing the signature from const to a function:

  A 'const' initializer in an ambient context must be a string or numeric literal or literal enum reference.

... (truncated)

Changelog

Sourced from lint-staged's changelog.

17.6.0

Minor Changes

• #1850 938d3f4 - Task functions like { title, task } can now use a logger function log() to emit output while the task runs. By default, the output will only be visible if the task fails, unless the --verbose option was used. Additionally, when the task rejects, the error will be shown in the output.

  import { defineConfig } from 'lint-staged/config'
  export default defineConfig({
  '*': {
  title: 'Fail if PDF files are committed',
  task: async (filepaths, { log }) => {
  const pdfFiles = filepaths.filter((f) => f.toLowerCase().endsWith('.pdf'))
  if (pdfFiles.length > 0) {
  log('PDF files should not be committed: %s', pdfFiles)
  throw new Error('Failed')
  }
  },
  },
  })

• #1854 30562bc - lint-staged now stages changes to all tracked files modified by tasks, including files that weren’t originally staged or didn’t match the configured globs. This can happen when your task has side-effects, or it's a function that ignores the staged files like () => "prettier --write .".

  If you have unstaged changes in a file and the task also edits that file, your unstaged changes will be staged too. Use --hide-unstaged to hide your changes while tasks run.

Patch Changes

• #1860 4296532 - The assignment of staged files to lint-staged configuration files (when using multiple, for example in a monorepo) has been rewritten to be more efficient. As a reminder, each staged file is assigned to exactly one configuration (the closest one), even if that config doesn't match the file in its globs.

• #1861 c45f28a - Fix running parallel tasks for a single glob, when tasks are created by a function. Nesting one level of arrays inside an array of tasks will result in the inner tasks running in parallel. This behavior should now be consistent when creating tasks using functions. In the following example eslint and prettier will run in parallel (for all files, when any JS files are staged):

  import { defineConfig } from 'lint-staged/config'
  export default defineConfig({
  '*.js': () => [['eslint --max-warnings=0 .', 'prettier --list-different .']],
  })

• #1859 f0ea69d - Various performance improvements from skipping redundant internal Git calls.

• #1856 69d7d17 - Partially staged changes are hidden in a uniquely-named patch file to avoid multiple invocations of lint-staged overwriting it. This makes it safer to run lint-staged in multiple worktrees at the same time.

17.5.1

Patch Changes

• #1852 bfcca94 - Fix TypeScript issue TS1254 from defineConfig() by changing the signature from const to a function:

... (truncated)

Commits

• See full diff in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for lint-staged since your current version.

Updates sinon from 11.1.2 to 22.1.0

Changelog

Sourced from sinon's changelog.

22.1.0

• d36e921b fix: let returns override returnsArg (王胜)

  Signed-off-by: 王胜 2318857637@qq.com

• 40c4caa0 fix: align restoreObject docs test with idempotent behavior (#2745) (Julia Miller)

  restoreObject was made idempotent in #2737 — it no longer throws for objects with no restorable methods. Updates the docs page and its corresponding test to reflect this.

• a68dac19 fix: throw a clear error when throwArg index equals the argument count (#2743) (spokodev)

  • fix: throw a clear error when throwArg index equals the argument count

  spyCall.throwArg(pos) guarded with pos > this.args.length, so calling it with pos equal to the number of recorded arguments slipped past the guard and reached throw this.args[pos], throwing undefined instead of the intended TypeError. A thrown undefined cannot be inspected as an Error and is reported by test frameworks as no exception thrown.

  Use >= to match ensureArgs in behavior.js and the sibling callArg helpers, which already reject an out-of-range index with a clear error.

• 9ea504e3 feat: make sinon.restoreObject idempotent (#2737) (Ilia Choly)

  Passing an object with no live fakes to restoreObject now restores nothing instead of throwing, giving it symmetry with sinon.restore() and sandbox.restore(). The strict "found no methods" check is retained for spy(object) and stub(object), which now use a dedicated walkObjectStrict export, while restoreObject uses the loose walkObject. Passing a falsy value still throws.

  Fixes #2736

• 4db4feff fix: preserve fake undefined argument validation (Vishal Kumar Singh)
• 755a40d7 fix: isolate callId counter per sandbox for parallel test support (Vishal Kumar Singh)

  The global callId counter in proxy-invoke.js caused calledImmediatelyBefore and calledImmediatelyAfter to fail when tests run in parallel with separate sandboxes. Each sandbox now maintains its own callId counter, passed through the spy/stub/fake creation chain via a context object.

  Fixes #2472

Released by Morgan Roderick on 2026-07-20.

22.0.0

• ed911df5 Update Ruby gems (Carl-Erik Kopseng)
• 75a1e5b8

... (truncated)

Commits

• ab289e9 22.1.0
• bb3b75a chore: remove Jekyll steps from version hook
• bb38f25 chore: run docs tests in preversion hook
• d36e921 fix: let returns override returnsArg
• 11db213 ci: run docs tests on every PR (#2746)
• 40c4caa fix: align restoreObject docs test with idempotent behavior (#2745)
• 5ccb7fd build(deps): bump the action-deps group with 4 updates (#2744)
• a68dac1 fix: throw a clear error when throwArg index equals the argument count (#2743)
• 9ea504e feat: make sinon.restoreObject idempotent (#2737)
• cf5d9e8 fix: remove dead link and exclude code example URLs from link check
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by mrgnrdrck, a new releaser for sinon since your current version.

Updates @types/sinon from 10.0.20 to 22.0.2

Commits

• See full diff in compare view

Updates ts-node from 10.1.0 to 10.9.2

Release notes

Sourced from ts-node's releases.

Fix tsconfig.json file not found

Fixed

• Fixed tsconfig.json file not found on latest TypeScript version (TypeStrong/ts-node#2091)

v10.9.1

Fixed

• Workaround nodejs bug introduced in 18.6.0 (#1838) @​cspotcode
  • Only affects projects on node >=18.6.0 using --esm
  • Older versions of node and projects without --esm are unaffected

TypeStrong/ts-node@v10.9.0...v10.9.1 https://github.com/TypeStrong/ts-node/milestone/18?closed=1

v10.9.0

Added

• --project accepts path to a directory containing a tsconfig.json (#1829, #1830) @​cspotcode
  • previously it required an explicit filename
• Added helpful error message when swc version is too old to support our configuration (#1802) @​cspotcode
• Added experimentalTsImportSpecifiers option which allows using voluntary .ts file extensions in import specifiers (undocumented except for API docs) (#1815) @​cspotcode

Fixed

• Fixed bug where child_process.fork() would erroneously execute the parent's entrypoint script, not the intended child script (#1812, #1814) @​devversion
• Fixed support for jsx modes "react-jsx" and "react-jsxdev" in swc transpiler (#1800, #1802) @​cspotcode
• Fixed support for import assertions in swc transpiler (#1817, #1802) @​cspotcode
• Fixed bug where calling repl.evalCode() with code not ending in a newline would not update the typechecker accordingly (#1764, #1824) @​cspotcode

TypeStrong/ts-node@v10.8.2...v10.9.0 https://github.com/TypeStrong/ts-node/milestone/16?closed=1

v10.8.2

Fixed

• Revert "Use file URL for source map paths" (#1821) @​cspotcode
  • Fixes #1790: ts-node 10.8.1 regression where nyc code coverage reports had incorrect paths
  • Fixes #1797: ts-node 10.8.1 regression where breakpoints did not hit in VSCode debugging
• Allow JSON imports in node 16.15 and up (#1792) @​queengooborg
  • JSON imports were already supported in v17.5 and up
  • this change extends support to >=16.15.0,<17.0.0
  • These version ranges match vanilla node's support for JSON imports

TypeStrong/ts-node@v10.8.1...v10.8.2 https://github.com/TypeStrong/ts-node/milestone/15?closed=1

v10.8.1

Fixed

... (truncated)

Commits

• 057ac1b 10.9.2
• c8805d5 Update package lock
• 99862f7 Bump swc dependency
• cdc4e88 Ignore test files in build schema
• 08cdfb0 Backport swc fixes on main
• 9639daa Ignore test files in build
• cc1a503 Fix tsconfig.json not found with TS >= 5.3 (#2091)
• 0e0da59 10.9.1
• c02af13 Attempt workaround for node regression (#1838)
• 11424e0 10.9.0
• Additional commits viewable in compare view

Updates typescript from 4.3.5 to 7.0.2

Release notes

Sourced from typescript's releases.

TypeScript 7.0.2

https://devblogs.microsoft.com/typescript/announcing-typescript-7-0/

This tag was originally released at: https://github.com/microsoft/typescript-go/releases/tag/typescript%2Fv7.0.2

TypeScript 6.0.3

For release notes, check out the release announcement blog post.

• fixed issues query for TypeScript 6.0.0 (Beta).
• fixed issues query for TypeScript 6.0.1 (RC).
• fixed issues query for TypeScript 6.0.2 (Stable).
• fixed issues query for TypeScript 6.0.3 (Stable).

Downloads are available on:

• npm

TypeScript 6.0

For release notes, check out the release announcement blog post.

• fixed issues query for TypeScript 6.0.0 (Beta).
• fixed issues query for TypeScript 6.0.1 (RC).
• fixed issues query for TypeScript 6.0.2 (Stable).

Downloads are available on:

• npm

TypeScript 6.0.1 RC

For release notes, check out the release announcement blog post.

• fixed issues query for TypeScript 6.0.0 (Beta).
• fixed issues query for TypeScript 6.0.1 (RC).

Downloads are available on:

• npm

TypeScript 6.0 Beta

For release notes, check out the release announcement.

• fixed issues query for Typescript 6.0.0 (Beta).

Downloads are available on:

• npm

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

... (truncated)

Commits

• 1e4744d Merge branch 'main' into ts7-release
• a5a219cmicrosoft/typescript-go#4558
• ecfe30d Update status localization
• 5de25b5 Hide executable name in TypeScript status
• d7ce74a Show bundled TypeScript version for packaged servers
• 29be66a Correct TS 7 release version to 7.0.2
• ed2bd1b Merge branch 'main' into ts7-release
• 8873075 Bump the github-actions group across 1 directory with 3 updates (microsoft/ty...
• 9427131 Set up stable / nightly extension split, other prep (microsoft/typescript-go#...
• d4eaca5microsoft/typescript-go#4549
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by microsoft1es, a new releaser for typescript since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions