fix(deps): update external major (major)

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
ini	6.0.0 → 7.0.0
lint-staged	16.4.0 → 17.0.4
sinon (source)	21.1.2 → 22.0.0

---

Release Notes

npm/ini (ini)

v7.0.0

Compare Source

⚠️ BREAKING CHANGES

• ini now supports node ^22.22.2 || ^24.15.0 || >=26.0.0
• template-oss-apply

Features

• 55b6841 #​301 bump to new node engine range (@​owlstronaut)
• 2b11ba8 #​301 template-oss-apply (@​owlstronaut)

Chores

• f6ed5be #​301 template-oss-apply (@​owlstronaut)
• a2c835e #​293 bump @​npmcli/eslint-config from 5.1.0 to 6.0.0 (#​293) (@​dependabot[bot])
• 3661dce #​296 bump @​npmcli/template-oss from 4.28.0 to 4.28.1 (#​296) (@​dependabot[bot], @​npm-cli-bot)

lint-staged/lint-staged (lint-staged)

v17.0.4

Compare Source

Patch Changes

• #​1788 f95c1f8 - Another fix for making sure lint-staged adds task modifications correctly to the commit in the following cases:

  • after editing <file> it is staged with git add <file>, and then committed with git commit
  • after editing <file> it is committed with git commit --all without explicit git add
  • after editing <file> it is committed with git commit <pathspec> without explicit git add

  There's new test cases which actually setup the Git pre_commit hook to run lint-staged and verify them. These issues started in v17.0.0 when trying to improve support for committig without having explicitly staged files.

v17.0.3

Compare Source

Patch Changes

• #​1782 06813f9 Thanks @​iiroj! - Fix lint-staged behavior when implicitly committing files without using git add by either:
  • git commit -am "my commit message" where -a (--all) means to automatically stage all tracked modified and deleted files
  • git commit -m "my commit message" . where . is an example of a pathspec where matching files will be staged

v17.0.2

Compare Source

Patch Changes

• #​1779 88670ca Thanks @​iiroj! - Enable immutable GitHub releases

v17.0.1

Compare Source

Patch Changes

• #​1776 4a5664b Thanks @​iiroj! - Adjust GitHub Actions workflow so that automatic publishing works with signed commits.

v17.0.0

Compare Source

Major Changes

• #​1745 e244adf Thanks @​iiroj! - Node.js v20 is no longer supported, and the oldest supported version is now 22.22.1, which is an active LTS version at the time of this release. Node.js 20 will be EOL after April 2026. Please upgrade your Node.js version!

• #​1676 0584e0b Thanks @​outslept! - Lint-staged now tries to verify the installed Git version is at least 2.32.0, released in 2021. If you're using an even older Git version, you need to upgrade it before running lint-staged!

• #​1745 2dcc40a Thanks @​iiroj! - The dependency yaml is now marked as optional and probably won't be installed by default. If you're using a YAML configuration file you should install the package separately:

  npm install --development yaml

  If you're using .lintstagedrc as the config file name (without a file extension), it will be treated as a YAML file. If the content is JSON, consider renaming it to .lintstagedrc.json to avoid needing to install yaml.

Minor Changes

• #​1748 809d5ef Thanks @​iiroj! - Add new option --hide-all for hiding all unstaged changes and untracked files, before running tasks. This makes it easier to run tools like Knip which check for unused code. Untracked files are included in the backup stash and restored automatically after running.

• #​1759 f13045a Thanks @​iiroj! - Update dependencies, including tinyexec@1.1.1 to fix the following issues:

  • When using a Node.js version manager with multiple versions installed (nvm, n, for example), scripts with the #!/usr/bin/env node shebang (Prettier, ESLint, for example) were previously spawned using the default Node.js version configured by the version manager (the one which node points to) on POSIX systems. Now, they will be spawned with the same version that lint-staged itself was started with.
    • For example, if your default Node.js version is 24.14.1 but lint-staged is run with the latest version 25.9.0, the tasks spawned by lint-staged will now also use version 25.9.0. Previously they were spawned using 24.14.1.
  • When installing Node.js from the Ubuntu App Center (Snap store), the node executable available in PATH is a symlink pointing to Snap itself. The sandboxing features of Snap prevented lint-staged from spawning scripts with the #!/usr/bin/env node shebang, because it meant lint-staged tried to spawn Snap via the symlink. This resulted in an ENOENT error when trying to run prettier, for example. Now, since the real node executable's directory is available in the PATH, lint-staged will instead spawn the script with the real node binary succesfully.

• #​1761 d3251b1 Thanks @​iiroj! - Lint-staged now runs git update-index --again after running tasks, instead of git add <originally staged files>. This should improve compatibility when using non-default indexes, for example when committing with a pathspec git commit -m "message" . instead of adding files to the index.

• #​1745 a9585ac Thanks @​iiroj! - Remove commander as a dependency and use the built-in parseArgs from node:util to parse CLI flags.

Patch Changes

• #​1755 c82d30b Thanks @​iiroj! - All tests now pass on the Bun runtime (latest).

• #​1750 a401818 Thanks @​iiroj! - Remove manual handling for git stash --keep-index resurrecting deleted files, because the issue was fixed in Git 2.23.0 and lint-staged requires at least Git 2.32.0.

• #​1771 c4b8936 Thanks @​iiroj! - Fix documentation about multiple config files and the --cwd option. When using it, all tasks will be run in the specified directory. For example, to run everything in the actual process.cwd(), use lint-staged --cwd=".".

sinonjs/sinon (sinon)

v22.0.0

Compare Source

• ed911df5
  Update Ruby gems (Carl-Erik Kopseng)
• 75a1e5b8
  Update to Node 26 (Carl-Erik Kopseng)
• 197d6608
  Update documentation on faking timers to reflect the current state of fake-timers (Carl-Erik Kopseng)
• c5ddf80b
  Update fake-timers@​15.4: includes new Temporal API (Carl-Erik Kopseng)
• f4ab02f6
  Update updatable packages (Carl-Erik Kopseng)
• 0536afc8
  Quality: Global mutable call id can grow unbounded across long-lived processes (#​2691) (tuanaiseo)

  • refactor: global mutable call id can grow unbounded across l

  callId is module-scoped and incremented on every invocation. In long-running test runners or embedded usage, this can grow indefinitely and eventually lose integer precision semantics for strict ordering comparisons.

  Affected files: proxy-invoke.js

  Signed-off-by: tuanaiseo 221258316+tuanaiseo@users.noreply.github.com

  • Wrap around for all values that are too high

  ---

  Signed-off-by: tuanaiseo 221258316+tuanaiseo@users.noreply.github.com
  Co-authored-by: Carl-Erik Kopseng carlerik@gmail.com

• f4f7d93b
  Perform additional cleanup when calling callThrough() (#​2670) (Cyrille)
• 6199e9e4
  improve GitHubworkflows by introducing zizmor for monitoring (#​2686) (Till!)

  • fix(workflows): fetch-depth is for actions/checkout

  • chore(workflows): update

  • pin all actions to precise commits
  • avoid credential leakage from actions/checkout
  • group action updates going forward
  • add zimor config to ignore "secrets outside env"
  • add job to keep validating workflows

• f7476b59
  Use path.normalize() for path normalization (Carl-Erik Kopseng)
• 2c975393
  fix: make build and node test scripts cross-platform (laplace young)
• a7692917
  fix: isolate walk state from Object prototype (laplace young)
• 66df977a
  Fix sinon.restore() cascade-restoring sub-sandboxes (#​2704) (Charlie Leitheiser)

  The ESM port of createApi (#​2683, shipped in 21.1.0) replaced createSandbox: createSandbox with a wrapper that pushes every newly-created sandbox into the root sandbox's fake collection:

  createSandbox: function createSandbox(config) {
      const s = createConfiguredSandbox(config);
      sandbox.getFakes().push(s);
      return s;
  }
  

  Sandbox#restore then walks that collection and calls .restore() on each entry. Because a sub-sandbox is itself an entry, every top-level sinon.restore() cascades into every sub-sandbox and undoes its stubs/timers/etc. — defeating the whole point of having an isolated sub-sandbox. The same cascade hits resetHistory and
  verifyAndRestore. This is the regression reported in #​2701.

  Restore the pre-21.1 behaviour: hand the root API a direct reference to createConfiguredSandbox. Sub-sandboxes are now isolated; only subSandbox.restore() (or verifyAndRestore) clears their fakes.

  Also flip the four sandbox tests that were locking in the buggy cascade: they now assert the parent's restore/resetHistory leaves the child untouched, with an explicit child-side cleanup at the
  end.

  Closes #​2701

• f0bd6e1b
  fix: exclude proto from walk() (#​2699) (Kevin Locke)

  __proto__ is a special property to access an object's prototype. It
  has many pitfalls:

  • Setting it to an object value changes an object's prototype, which is
    generally discouraged and may be unexpected by the iterator callback.
  • Setting it to a non-object value does nothing (meaning seen[k] = true has no effect).
  • When Node.js is run with the --disable-proto=throw option, getting
    or setting __proto__ causes an exception with code
    ERR_PROTO_ACCESS to be thrown.

  Additionally, since this property (and all properties of
  Object.prototype) are currently unused in this project by consumers of
  walk(), it is both safe and preferable to exclude.

  Fixes: #​2695

  Signed-off-by: Kevin Locke kevin@kevinlocke.name

• 1f8afd50
  chore: add context7.json for ownership confirmation (Morgan Roderick)

Released by Carl-Erik Kopseng on 2026-05-05.

---

Configuration

📅 Schedule: (in timezone Europe/Zurich)

• Branch creation
  • "after 2pm on Monday"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[github-actions]

This PR will trigger a patch release when merged.