[PR #715] [MERGED] chore(deps-dev): bump lint-staged from 15.5.1 to 16.1.2 in /web #721

New issue

Closed

opened 2026-03-03 16:39:47 +03:00 by kerem · 0 comments

kerem commented

2026-03-03 16:39:47 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/NdoleStudio/httpsms/pull/715
Author: @dependabot[bot]
Created: 8/1/2025
Status: ✅ Merged
Merged: 8/7/2025
Merged by: @AchoArnold

Base: main ← Head: dependabot/npm_and_yarn/web/lint-staged-16.1.2

📝 Commits (1)

95381b6 chore(deps-dev): bump lint-staged from 15.5.1 to 16.1.2 in /web

📊 Changes

2 files changed (+38 additions, -51 deletions)

View changed files

📝 web/package.json (+1 -1)
📝 web/pnpm-lock.yaml (+37 -50)

📄 Description

Bumps lint-staged from 15.5.1 to 16.1.2.

Release notes

Sourced from lint-staged's releases.

v16.1.2

Patch Changes

#1570 a7c0c88 Thanks @ItsNickBarry! - When using --diff-filter with the D option to include deleted staged files, lint-staged no longer tries to stage the deleted files, unless they're no longer deleted. Previously this caused an error from git add like fatal: pathspec 'deleted-file' did not match any files.

38f942e Thanks @iiroj! - Removed an extraneous log entry that printed shouldHidePArtiallyStagedFiles to console output.

v16.1.1

Patch Changes

#1565 3686977 Thanks @iiroj! - Lint-staged now explicitly warns about potential data loss when using --no-stash.

#1571 02299a9 Thanks @iiroj! - Function tasks (introduced in v16.0.0) only receive the staged files matching the configured glob, instead of all staged files.

#1563 bc61c74 Thanks @iiroj! - This version fixes incorrect behavior where unstaged changes were committed when using the --no-stash option. This happened because --no-stash implied --no-hide-partially-staged, meaning unstaged changes to files which also had other staged changes were added to the commit by lint-staged; this is no longer the case.

The previous (incorrect) behavior can still be achieved by using both options --no-stash --no-hide-partially-staged at the same time.

v16.1.0

Minor Changes

#1536 e729daa Thanks @iiroj! - A new flag --no-revert has been introduced for when task modifications should be applied to the index before aborting the commit in case of errors. By default, lint-staged will clear all task modifications and revert to the original state.

#1550 b27fa3f Thanks @iiroj! - Lint-staged now ignores symlinks and leaves them out from the list of staged files.

Patch Changes

#1558 c37dc38 Thanks @iiroj! - The minimum required Node.js version is lowered to 20.17 following nano-spawn@1.0.2.

v16.0.0

Major Changes
#1546 158d15c Thanks @iiroj! - Processes are spawned using nano-spawn instead of execa. If you are using Node.js scripts as tasks, you might need to explicitly run them with node, especially when using Windows:
{
  "*.js": "node my-js-linter.js"
}
#1546 158d15c Thanks @iiroj! - The --shell flag has been removed and lint-staged no longer supports evaluating commands directly via a shell. To migrate existing commands, you can create a shell script and invoke it instead. Lint-staged will pass matched staged files as a list of arguments, accessible via "$@":
# my-script.sh
#!/bin/bash
echo "Staged files: $@"
and

... (truncated)

Changelog

Sourced from lint-staged's changelog.

16.1.2

Patch Changes

#1570 a7c0c88 Thanks @ItsNickBarry! - When using --diff-filter with the D option to include deleted staged files, lint-staged no longer tries to stage the deleted files, unless they're no longer deleted. Previously this caused an error from git add like fatal: pathspec 'deleted-file' did not match any files.

38f942e Thanks @iiroj! - Removed an extraneous log entry that printed shouldHidePArtiallyStagedFiles to console output.

16.1.1

Patch Changes

#1565 3686977 Thanks @iiroj! - Lint-staged now explicitly warns about potential data loss when using --no-stash.

#1571 02299a9 Thanks @iiroj! - Function tasks (introduced in v16.0.0) only receive the staged files matching the configured glob, instead of all staged files.

#1563 bc61c74 Thanks @iiroj! - This version fixes incorrect behavior where unstaged changes were committed when using the --no-stash option. This happened because --no-stash implied --no-hide-partially-staged, meaning unstaged changes to files which also had other staged changes were added to the commit by lint-staged; this is no longer the case.

The previous (incorrect) behavior can still be achieved by using both options --no-stash --no-hide-partially-staged at the same time.

16.1.0

Minor Changes

#1536 e729daa Thanks @iiroj! - A new flag --no-revert has been introduced for when task modifications should be applied to the index before aborting the commit in case of errors. By default, lint-staged will clear all task modifications and revert to the original state.

#1550 b27fa3f Thanks @iiroj! - Lint-staged now ignores symlinks and leaves them out from the list of staged files.

Patch Changes

#1558 c37dc38 Thanks @iiroj! - The minimum required Node.js version is lowered to 20.17 following nano-spawn@1.0.2.

16.0.0

Major Changes
#1546 158d15c Thanks @iiroj! - Processes are spawned using nano-spawn instead of execa. If you are using Node.js scripts as tasks, you might need to explicitly run them with node, especially when using Windows:
{
  "*.js": "node my-js-linter.js"
}
#1546 158d15c Thanks @iiroj! - The --shell flag has been removed and lint-staged no longer supports evaluating commands directly via a shell. To migrate existing commands, you can create a shell script and invoke it instead. Lint-staged will pass matched staged files as a list of arguments, accessible via "$@":
# my-script.sh
#!/bin/bash

... (truncated)

Commits

0c48e29 chore(changeset): release
e07227e perf: call rev-parse only once instead of three times when resolving git repo
38f942e fix: remove extra log entry
5031a71 perf: further optimize file chunking
6ec38b9 perf: optimize file list length calculation (#1581)
a7c0c88 fix: only stage changes to deleted files if they're no longer deleted after r...
ccd5edd test: pass --no-error-on-unmatched-pattern to prettier command in --diff-opti...
48a6e95 test: add failing test for staged deleted files not passed directly to tasks ...
b56b29e test: add failing test for staged deleted files with diff filter D
8420429 chore(changeset): release
Additional commits viewable in compare view

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 merge will merge this PR after your CI passes on it
@dependabot squash and merge will squash and merge this PR after your CI passes on it
@dependabot cancel merge will cancel a previously requested merge and block automerging
@dependabot reopen will reopen this PR if it is closed
@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
@dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
@dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
@dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/NdoleStudio/httpsms/pull/715 **Author:** [@dependabot[bot]](https://github.com/apps/dependabot) **Created:** 8/1/2025 **Status:** ✅ Merged **Merged:** 8/7/2025 **Merged by:** [@AchoArnold](https://github.com/AchoArnold) **Base:** `main` ← **Head:** `dependabot/npm_and_yarn/web/lint-staged-16.1.2` --- ### 📝 Commits (1) - [`95381b6`](https://github.com/NdoleStudio/httpsms/commit/95381b66095a84fc57cfecadd6e101054412d788) chore(deps-dev): bump lint-staged from 15.5.1 to 16.1.2 in /web ### 📊 Changes **2 files changed** (+38 additions, -51 deletions) <details> <summary>View changed files</summary> 📝 `web/package.json` (+1 -1) 📝 `web/pnpm-lock.yaml` (+37 -50) </details> ### 📄 Description Bumps [lint-staged](https://github.com/lint-staged/lint-staged) from 15.5.1 to 16.1.2. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/lint-staged/lint-staged/releases">lint-staged's releases</a>.</em></p> <blockquote> <h2>v16.1.2</h2> <h3>Patch Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/lint-staged/lint-staged/pull/1570">#1570</a> <a href="https://github.com/lint-staged/lint-staged/commit/a7c0c88bcfe94e695528cb33e69fea58586691fc"><code>a7c0c88</code></a> Thanks <a href="https://github.com/ItsNickBarry"><code>@ItsNickBarry</code></a>! - When using <code>--diff-filter</code> with the <code>D</code> option to include deleted staged files, <em>lint-staged</em> no longer tries to stage the deleted files, unless they're no longer deleted. Previously this caused an error from <code>git add</code> like <code>fatal: pathspec 'deleted-file' did not match any files</code>.</p> </li> <li> <p><a href="https://github.com/lint-staged/lint-staged/commit/38f942ecc456355d5f12af68db1696f3411f65c2"><code>38f942e</code></a> Thanks <a href="https://github.com/iiroj"><code>@iiroj</code></a>! - Removed an extraneous log entry that printed <code>shouldHidePArtiallyStagedFiles</code> to console output.</p> </li> </ul> <h2>v16.1.1</h2> <h3>Patch Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/lint-staged/lint-staged/pull/1565">#1565</a> <a href="https://github.com/lint-staged/lint-staged/commit/3686977ccdadf70b709c16c0346ef6c2b18e2376"><code>3686977</code></a> Thanks <a href="https://github.com/iiroj"><code>@iiroj</code></a>! - <em>Lint-staged</em> now explicitly warns about potential data loss when using <code>--no-stash</code>.</p> </li> <li> <p><a href="https://redirect.github.com/lint-staged/lint-staged/pull/1571">#1571</a> <a href="https://github.com/lint-staged/lint-staged/commit/02299a9e4f98a05c13beb27f3596af73aaa8c150"><code>02299a9</code></a> Thanks <a href="https://github.com/iiroj"><code>@iiroj</code></a>! - Function tasks (introduced in v16.0.0) only receive the staged files matching the configured glob, instead of all staged files.</p> </li> <li> <p><a href="https://redirect.github.com/lint-staged/lint-staged/pull/1563">#1563</a> <a href="https://github.com/lint-staged/lint-staged/commit/bc61c74383b6d100c55b8d275b979d583ffbe5a1"><code>bc61c74</code></a> Thanks <a href="https://github.com/iiroj"><code>@iiroj</code></a>! - This version fixes incorrect behavior where unstaged changes were committed when using the <code>--no-stash</code> option. This happened because <code>--no-stash</code> implied <code>--no-hide-partially-staged</code>, meaning unstaged changes to files which also had other staged changes were added to the commit by <em>lint-staged</em>; this is no longer the case.</p> <p>The previous (incorrect) behavior can still be achieved by using both options <code>--no-stash --no-hide-partially-staged</code> at the same time.</p> </li> </ul> <h2>v16.1.0</h2> <h3>Minor Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/lint-staged/lint-staged/pull/1536">#1536</a> <a href="https://github.com/lint-staged/lint-staged/commit/e729daa3b3ae28e613f63e730652dbfad5d1c594"><code>e729daa</code></a> Thanks <a href="https://github.com/iiroj"><code>@iiroj</code></a>! - A new flag <code>--no-revert</code> has been introduced for when task modifications should be applied to the index before aborting the commit in case of errors. By default, <em>lint-staged</em> will clear all task modifications and revert to the original state.</p> </li> <li> <p><a href="https://redirect.github.com/lint-staged/lint-staged/pull/1550">#1550</a> <a href="https://github.com/lint-staged/lint-staged/commit/b27fa3fecb75bcdcaa4bcd483c9d5c0755a22607"><code>b27fa3f</code></a> Thanks <a href="https://github.com/iiroj"><code>@iiroj</code></a>! - <em>Lint-staged</em> now ignores symlinks and leaves them out from the list of staged files.</p> </li> </ul> <h3>Patch Changes</h3> <ul> <li><a href="https://redirect.github.com/lint-staged/lint-staged/pull/1558">#1558</a> <a href="https://github.com/lint-staged/lint-staged/commit/c37dc38dddbdebc41df4dbd909d79c98c3f69eb3"><code>c37dc38</code></a> Thanks <a href="https://github.com/iiroj"><code>@iiroj</code></a>! - The minimum required Node.js version is lowered to <code>20.17</code> following <a href="https://github.com/sindresorhus/nano-spawn/releases/tag/v1.0.2">nano-spawn@1.0.2</a>.</li> </ul> <h2>v16.0.0</h2> <h3>Major Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/lint-staged/lint-staged/pull/1546">#1546</a> <a href="https://github.com/lint-staged/lint-staged/commit/158d15c9aea0a3a87790ec3766442763cf387dba"><code>158d15c</code></a> Thanks <a href="https://github.com/iiroj"><code>@iiroj</code></a>! - Processes are spawned using <a href="https://github.com/sindresorhus/nano-spawn">nano-spawn</a> instead of <a href="https://github.com/sindresorhus/execa">execa</a>. If you are using Node.js scripts as tasks, you might need to explicitly run them with <code>node</code>, especially when using Windows:</p> <pre lang="json"><code>{ "*.js": "node my-js-linter.js" } </code></pre> </li> <li> <p><a href="https://redirect.github.com/lint-staged/lint-staged/pull/1546">#1546</a> <a href="https://github.com/lint-staged/lint-staged/commit/158d15c9aea0a3a87790ec3766442763cf387dba"><code>158d15c</code></a> Thanks <a href="https://github.com/iiroj"><code>@iiroj</code></a>! - The <code>--shell</code> flag has been removed and <em>lint-staged</em> no longer supports evaluating commands directly via a shell. To migrate existing commands, you can create a shell script and invoke it instead. Lint-staged will pass matched staged files as a list of arguments, accessible via <code>"$@"</code>:</p> <pre lang="shell"><code># my-script.sh #!/bin/bash <p>echo "Staged files: $@"<br /> </code></pre></p> <p>and</p> </li> </ul>  </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/lint-staged/lint-staged/blob/main/CHANGELOG.md">lint-staged's changelog</a>.</em></p> <blockquote> <h2>16.1.2</h2> <h3>Patch Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/lint-staged/lint-staged/pull/1570">#1570</a> <a href="https://github.com/lint-staged/lint-staged/commit/a7c0c88bcfe94e695528cb33e69fea58586691fc"><code>a7c0c88</code></a> Thanks <a href="https://github.com/ItsNickBarry"><code>@ItsNickBarry</code></a>! - When using <code>--diff-filter</code> with the <code>D</code> option to include deleted staged files, <em>lint-staged</em> no longer tries to stage the deleted files, unless they're no longer deleted. Previously this caused an error from <code>git add</code> like <code>fatal: pathspec 'deleted-file' did not match any files</code>.</p> </li> <li> <p><a href="https://github.com/lint-staged/lint-staged/commit/38f942ecc456355d5f12af68db1696f3411f65c2"><code>38f942e</code></a> Thanks <a href="https://github.com/iiroj"><code>@iiroj</code></a>! - Removed an extraneous log entry that printed <code>shouldHidePArtiallyStagedFiles</code> to console output.</p> </li> </ul> <h2>16.1.1</h2> <h3>Patch Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/lint-staged/lint-staged/pull/1565">#1565</a> <a href="https://github.com/lint-staged/lint-staged/commit/3686977ccdadf70b709c16c0346ef6c2b18e2376"><code>3686977</code></a> Thanks <a href="https://github.com/iiroj"><code>@iiroj</code></a>! - <em>Lint-staged</em> now explicitly warns about potential data loss when using <code>--no-stash</code>.</p> </li> <li> <p><a href="https://redirect.github.com/lint-staged/lint-staged/pull/1571">#1571</a> <a href="https://github.com/lint-staged/lint-staged/commit/02299a9e4f98a05c13beb27f3596af73aaa8c150"><code>02299a9</code></a> Thanks <a href="https://github.com/iiroj"><code>@iiroj</code></a>! - Function tasks (introduced in v16.0.0) only receive the staged files matching the configured glob, instead of all staged files.</p> </li> <li> <p><a href="https://redirect.github.com/lint-staged/lint-staged/pull/1563">#1563</a> <a href="https://github.com/lint-staged/lint-staged/commit/bc61c74383b6d100c55b8d275b979d583ffbe5a1"><code>bc61c74</code></a> Thanks <a href="https://github.com/iiroj"><code>@iiroj</code></a>! - This version fixes incorrect behavior where unstaged changes were committed when using the <code>--no-stash</code> option. This happened because <code>--no-stash</code> implied <code>--no-hide-partially-staged</code>, meaning unstaged changes to files which also had other staged changes were added to the commit by <em>lint-staged</em>; this is no longer the case.</p> <p>The previous (incorrect) behavior can still be achieved by using both options <code>--no-stash --no-hide-partially-staged</code> at the same time.</p> </li> </ul> <h2>16.1.0</h2> <h3>Minor Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/lint-staged/lint-staged/pull/1536">#1536</a> <a href="https://github.com/lint-staged/lint-staged/commit/e729daa3b3ae28e613f63e730652dbfad5d1c594"><code>e729daa</code></a> Thanks <a href="https://github.com/iiroj"><code>@iiroj</code></a>! - A new flag <code>--no-revert</code> has been introduced for when task modifications should be applied to the index before aborting the commit in case of errors. By default, <em>lint-staged</em> will clear all task modifications and revert to the original state.</p> </li> <li> <p><a href="https://redirect.github.com/lint-staged/lint-staged/pull/1550">#1550</a> <a href="https://github.com/lint-staged/lint-staged/commit/b27fa3fecb75bcdcaa4bcd483c9d5c0755a22607"><code>b27fa3f</code></a> Thanks <a href="https://github.com/iiroj"><code>@iiroj</code></a>! - <em>Lint-staged</em> now ignores symlinks and leaves them out from the list of staged files.</p> </li> </ul> <h3>Patch Changes</h3> <ul> <li><a href="https://redirect.github.com/lint-staged/lint-staged/pull/1558">#1558</a> <a href="https://github.com/lint-staged/lint-staged/commit/c37dc38dddbdebc41df4dbd909d79c98c3f69eb3"><code>c37dc38</code></a> Thanks <a href="https://github.com/iiroj"><code>@iiroj</code></a>! - The minimum required Node.js version is lowered to <code>20.17</code> following <a href="https://github.com/sindresorhus/nano-spawn/releases/tag/v1.0.2">nano-spawn@1.0.2</a>.</li> </ul> <h2>16.0.0</h2> <h3>Major Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/lint-staged/lint-staged/pull/1546">#1546</a> <a href="https://github.com/lint-staged/lint-staged/commit/158d15c9aea0a3a87790ec3766442763cf387dba"><code>158d15c</code></a> Thanks <a href="https://github.com/iiroj"><code>@iiroj</code></a>! - Processes are spawned using <a href="https://github.com/sindresorhus/nano-spawn">nano-spawn</a> instead of <a href="https://github.com/sindresorhus/execa">execa</a>. If you are using Node.js scripts as tasks, you might need to explicitly run them with <code>node</code>, especially when using Windows:</p> <pre lang="json"><code>{ "*.js": "node my-js-linter.js" } </code></pre> </li> <li> <p><a href="https://redirect.github.com/lint-staged/lint-staged/pull/1546">#1546</a> <a href="https://github.com/lint-staged/lint-staged/commit/158d15c9aea0a3a87790ec3766442763cf387dba"><code>158d15c</code></a> Thanks <a href="https://github.com/iiroj"><code>@iiroj</code></a>! - The <code>--shell</code> flag has been removed and <em>lint-staged</em> no longer supports evaluating commands directly via a shell. To migrate existing commands, you can create a shell script and invoke it instead. Lint-staged will pass matched staged files as a list of arguments, accessible via <code>"$@"</code>:</p> <pre lang="shell"><code># my-script.sh #!/bin/bash <p></code></pre></p> </li> </ul>  </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/lint-staged/lint-staged/commit/0c48e29875c334487d250ab164e96febf8dfab5a"><code>0c48e29</code></a> chore(changeset): release</li> <li><a href="https://github.com/lint-staged/lint-staged/commit/e07227e987244c8806570c29be6e3012d54564a5"><code>e07227e</code></a> perf: call rev-parse only once instead of three times when resolving git repo</li> <li><a href="https://github.com/lint-staged/lint-staged/commit/38f942ecc456355d5f12af68db1696f3411f65c2"><code>38f942e</code></a> fix: remove extra log entry</li> <li><a href="https://github.com/lint-staged/lint-staged/commit/5031a71dd22961e69881b4d8deda67904d570d3a"><code>5031a71</code></a> perf: further optimize file chunking</li> <li><a href="https://github.com/lint-staged/lint-staged/commit/6ec38b9acf02ee55d0c6bcbdb40a9e5c7bbd0571"><code>6ec38b9</code></a> perf: optimize file list length calculation (<a href="https://redirect.github.com/lint-staged/lint-staged/issues/1581">#1581</a>)</li> <li><a href="https://github.com/lint-staged/lint-staged/commit/a7c0c88bcfe94e695528cb33e69fea58586691fc"><code>a7c0c88</code></a> fix: only stage changes to deleted files if they're no longer deleted after r...</li> <li><a href="https://github.com/lint-staged/lint-staged/commit/ccd5edd8955f2ce8577bc381a083062598c8ca2c"><code>ccd5edd</code></a> test: pass --no-error-on-unmatched-pattern to prettier command in --diff-opti...</li> <li><a href="https://github.com/lint-staged/lint-staged/commit/48a6e952d11feeb2bd194a08a62f28c8f7e83614"><code>48a6e95</code></a> test: add failing test for staged deleted files not passed directly to tasks ...</li> <li><a href="https://github.com/lint-staged/lint-staged/commit/b56b29efe637e3fee836e5bcc1c25354f70d5fc0"><code>b56b29e</code></a> test: add failing test for staged deleted files with diff filter D</li> <li><a href="https://github.com/lint-staged/lint-staged/commit/8420429b9d7c007f724e95ec301e492af3be351a"><code>8420429</code></a> chore(changeset): release</li> <li>Additional commits viewable in <a href="https://github.com/lint-staged/lint-staged/compare/v15.5.1...v16.1.2">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=lint-staged&package-manager=npm_and_yarn&previous-version=15.5.1&new-version=16.1.2)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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 merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>