dependabot[bot] opened a new pull request, #3499: URL: https://github.com/apache/tinkerpop/pull/3499
Bumps [lint-staged](https://github.com/lint-staged/lint-staged) from 16.4.0 to 17.0.8. <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>v17.0.8</h2> <h3>Patch Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/lint-staged/lint-staged/pull/1809";>#1809</a> <a href="https://github.com/lint-staged/lint-staged/commit/179b4372b2528f6fa66f927337d238711694d0e0";><code>179b437</code></a> - Fix <em>lint-staged</em> discarding the ongoing merge conflict status (<code>.git/MERGE_HEAD</code>) when using the <code>--hide-unstaged</code> or <code>--hide-all</code> options.</p> </li> <li> <p><a href="https://redirect.github.com/lint-staged/lint-staged/pull/1811";>#1811</a> <a href="https://github.com/lint-staged/lint-staged/commit/3d0b2c0709a2a39aa7b134e3741fed21250d808e";><code>3d0b2c0</code></a> - Fix issues with Git commands that are successful but also emit warnings to <code>stderr</code>, by ignoring the <code>stderr</code> output completely when the process exits with code 0. This was the behavior when using <code>nano-spawn</code> and <code>execa</code>, but when switching to <code>tinyexec</code> in 16.3.0 both <code>stdout</code> and <code>stderr</code> were used as interleaved output.</p> </li> </ul> <h2>v17.0.7</h2> <h3>Patch Changes</h3> <ul> <li><a href="https://redirect.github.com/lint-staged/lint-staged/pull/1806";>#1806</a> <a href="https://github.com/lint-staged/lint-staged/commit/e692e58ced9eae65b2077435b7e799c632f3db07";><code>e692e58</code></a> - Update dependency <code>tinyexec@^1.2.4</code>.</li> </ul> <h2>v17.0.6</h2> <h3>Patch Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/lint-staged/lint-staged/pull/1803";>#1803</a> <a href="https://github.com/lint-staged/lint-staged/commit/bdf27700a6e25b40333672eef4d438984a2d0383";><code>bdf2770</code></a> - Run all tests with <a href="https://deno.com";>Deno</a>, in addition to Node.js and Bun.</p> </li> <li> <p><a href="https://redirect.github.com/lint-staged/lint-staged/pull/1796";>#1796</a> <a href="https://github.com/lint-staged/lint-staged/commit/75082727cdd070adb59d62c9040515da3bbbb2f9";><code>7508272</code></a> - Fix performance regression of <em>lint-staged</em> v17 by going back to using <code>git add</code> to stage task modifications. This was changed to <code>git update-index --again</code> in v17 for less manual work, but unfortunately the <code>update-index</code> command gets slower in very large Git repos.</p> </li> <li> <p><a href="https://redirect.github.com/lint-staged/lint-staged/pull/1797";>#1797</a> <a href="https://github.com/lint-staged/lint-staged/commit/7b2505a1f8fb8735e6306c7dabdd5295632f8c1a";><code>7b2505a</code></a> - This version of <em>lint-staged</em> uses the new <a href="https://docs.npmjs.com/staged-publishing";>staged publishing for npm packages</a> feature. Releases are already published from GitHub Actions with <a href="https://docs.npmjs.com/trusted-publishers";>trusted publishing</a>, but now an additional approval with two-factor authentication is also required.</p> </li> <li> <p><a href="https://redirect.github.com/lint-staged/lint-staged/pull/1802";>#1802</a> <a href="https://github.com/lint-staged/lint-staged/commit/321b0a972a434006f5b5fac18867974ef040d037";><code>321b0a9</code></a> - Downgrade dependency <code>[email protected]</code> to avoid issues in version 1.2.3.</p> </li> </ul> <h2>v17.0.5</h2> <h3>Patch Changes</h3> <ul> <li><a href="https://redirect.github.com/lint-staged/lint-staged/pull/1792";>#1792</a> <a href="https://github.com/lint-staged/lint-staged/commit/1f672718b6fa67e0f00aafe107cb9f084f4d9102";><code>1f67271</code></a> - Correctly set the <code>--max-arg-length</code> default value based on the running platform. This controls how very long lists of staged files are split into multiple chunks.</li> </ul> <h2>v17.0.4</h2> <h3>Patch Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/lint-staged/lint-staged/pull/1788";>#1788</a> <a href="https://github.com/lint-staged/lint-staged/commit/f95c1f8df3368758c44c2052e568aac1b3d4c767";><code>f95c1f8</code></a> - Another fix for making sure <em>lint-staged</em> adds task modifications correctly to the commit in the following cases:</p> <ul> <li>after editing <code><file></code> it is staged with <code>git add <file></code>, and then committed with <code>git commit</code></li> <li>after editing <code><file></code> it is committed with <code>git commit --all</code> without explicit <code>git add</code></li> <li>after editing <code><file></code> it is committed with <code>git commit <pathspec></code> without explicit <code>git add</code></li> </ul> <p>There's new test cases which actually setup the Git <code>pre_commit</code> hook to run <em>lint-staged</em> and verify them. These issues started in <strong>v17.0.0</strong> when trying to improve support for committig without having explicitly staged files.</p> </li> </ul> <h2>v17.0.3</h2> <h3>Patch Changes</h3> <ul> <li><a href="https://redirect.github.com/lint-staged/lint-staged/pull/1782";>#1782</a> <a href="https://github.com/lint-staged/lint-staged/commit/06813f9ab661db987e7720086ef9ec3f552ee097";><code>06813f9</code></a> Thanks <a href="https://github.com/iiroj";><code>@iiroj</code></a>! - Fix <em>lint-staged</em> behavior when implicitly committing files without using <code>git add</code> by either: <ul> <li><code>git commit -am "my commit message"</code> where <code>-a</code> (<code>--all</code>) means to automatically stage all tracked modified and deleted files</li> <li><code>git commit -m "my commit message" .</code> where <code>.</code> is an example of a <a href="https://git-scm.com/docs/git-commit#Documentation/git-commit.txt-pathspec";><em>pathspec</em></a> where matching files will be staged</li> </ul> </li> </ul> <h2>v17.0.2</h2> <h3>Patch Changes</h3> <ul> <li><a href="https://redirect.github.com/lint-staged/lint-staged/pull/1779";>#1779</a> <a href="https://github.com/lint-staged/lint-staged/commit/88670ca2278200f6348ed663358895ddc4bfff3c";><code>88670ca</code></a> Thanks <a href="https://github.com/iiroj";><code>@iiroj</code></a>! - Enable immutable GitHub releases</li> </ul> <!-- raw HTML omitted --> </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>17.0.8</h2> <h3>Patch Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/lint-staged/lint-staged/pull/1809";>#1809</a> <a href="https://github.com/lint-staged/lint-staged/commit/179b4372b2528f6fa66f927337d238711694d0e0";><code>179b437</code></a> - Fix <em>lint-staged</em> discarding the ongoing merge conflict status (<code>.git/MERGE_HEAD</code>) when using the <code>--hide-unstaged</code> or <code>--hide-all</code> options.</p> </li> <li> <p><a href="https://redirect.github.com/lint-staged/lint-staged/pull/1811";>#1811</a> <a href="https://github.com/lint-staged/lint-staged/commit/3d0b2c0709a2a39aa7b134e3741fed21250d808e";><code>3d0b2c0</code></a> - Fix issues with Git commands that are successful but also emit warnings to <code>stderr</code>, by ignoring the <code>stderr</code> output completely when the process exits with code 0. This was the behavior when using <code>nano-spawn</code> and <code>execa</code>, but when switching to <code>tinyexec</code> in 16.3.0 both <code>stdout</code> and <code>stderr</code> were used as interleaved output.</p> </li> </ul> <h2>17.0.7</h2> <h3>Patch Changes</h3> <ul> <li><a href="https://redirect.github.com/lint-staged/lint-staged/pull/1806";>#1806</a> <a href="https://github.com/lint-staged/lint-staged/commit/e692e58ced9eae65b2077435b7e799c632f3db07";><code>e692e58</code></a> - Update dependency <code>tinyexec@^1.2.4</code>.</li> </ul> <h2>17.0.6</h2> <h3>Patch Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/lint-staged/lint-staged/pull/1803";>#1803</a> <a href="https://github.com/lint-staged/lint-staged/commit/bdf27700a6e25b40333672eef4d438984a2d0383";><code>bdf2770</code></a> - Run all tests with <a href="https://deno.com";>Deno</a>, in addition to Node.js and Bun.</p> </li> <li> <p><a href="https://redirect.github.com/lint-staged/lint-staged/pull/1796";>#1796</a> <a href="https://github.com/lint-staged/lint-staged/commit/75082727cdd070adb59d62c9040515da3bbbb2f9";><code>7508272</code></a> - Fix performance regression of <em>lint-staged</em> v17 by going back to using <code>git add</code> to stage task modifications. This was changed to <code>git update-index --again</code> in v17 for less manual work, but unfortunately the <code>update-index</code> command gets slower in very large Git repos.</p> </li> <li> <p><a href="https://redirect.github.com/lint-staged/lint-staged/pull/1797";>#1797</a> <a href="https://github.com/lint-staged/lint-staged/commit/7b2505a1f8fb8735e6306c7dabdd5295632f8c1a";><code>7b2505a</code></a> - This version of <em>lint-staged</em> uses the new <a href="https://docs.npmjs.com/staged-publishing";>staged publishing for npm packages</a> feature. Releases are already published from GitHub Actions with <a href="https://docs.npmjs.com/trusted-publishers";>trusted publishing</a>, but now an additional approval with two-factor authentication is also required.</p> </li> <li> <p><a href="https://redirect.github.com/lint-staged/lint-staged/pull/1802";>#1802</a> <a href="https://github.com/lint-staged/lint-staged/commit/321b0a972a434006f5b5fac18867974ef040d037";><code>321b0a9</code></a> - Downgrade dependency <code>[email protected]</code> to avoid issues in version 1.2.3.</p> </li> </ul> <h2>17.0.5</h2> <h3>Patch Changes</h3> <ul> <li><a href="https://redirect.github.com/lint-staged/lint-staged/pull/1792";>#1792</a> <a href="https://github.com/lint-staged/lint-staged/commit/1f672718b6fa67e0f00aafe107cb9f084f4d9102";><code>1f67271</code></a> - Correctly set the <code>--max-arg-length</code> default value based on the running platform. This controls how very long lists of staged files are split into multiple chunks.</li> </ul> <h2>17.0.4</h2> <h3>Patch Changes</h3> <ul> <li> <p><a href="https://redirect.github.com/lint-staged/lint-staged/pull/1788";>#1788</a> <a href="https://github.com/lint-staged/lint-staged/commit/f95c1f8df3368758c44c2052e568aac1b3d4c767";><code>f95c1f8</code></a> - Another fix for making sure <em>lint-staged</em> adds task modifications correctly to the commit in the following cases:</p> <ul> <li>after editing <code><file></code> it is staged with <code>git add <file></code>, and then committed with <code>git commit</code></li> <li>after editing <code><file></code> it is committed with <code>git commit --all</code> without explicit <code>git add</code></li> <li>after editing <code><file></code> it is committed with <code>git commit <pathspec></code> without explicit <code>git add</code></li> </ul> <p>There's new test cases which actually setup the Git <code>pre_commit</code> hook to run <em>lint-staged</em> and verify them. These issues started in <strong>v17.0.0</strong> when trying to improve support for committig without having explicitly staged files.</p> </li> </ul> <h2>17.0.3</h2> <h3>Patch Changes</h3> <ul> <li><a href="https://redirect.github.com/lint-staged/lint-staged/pull/1782";>#1782</a> <a href="https://github.com/lint-staged/lint-staged/commit/06813f9ab661db987e7720086ef9ec3f552ee097";><code>06813f9</code></a> Thanks <a href="https://github.com/iiroj";><code>@iiroj</code></a>! - Fix <em>lint-staged</em> behavior when implicitly committing files without using <code>git add</code> by either: <ul> <li><code>git commit -am "my commit message"</code> where <code>-a</code> (<code>--all</code>) means to automatically stage all tracked modified and deleted files</li> <li><code>git commit -m "my commit message" .</code> where <code>.</code> is an example of a <a href="https://git-scm.com/docs/git-commit#Documentation/git-commit.txt-pathspec";><em>pathspec</em></a> where matching files will be staged</li> </ul> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/lint-staged/lint-staged/commit/5f3b8f28e895972bd5a2cdba733327b49859b91f";><code>5f3b8f2</code></a> Merge pull request <a href="https://redirect.github.com/lint-staged/lint-staged/issues/1812";>#1812</a> from lint-staged/changeset-release/main</li> <li><a href="https://github.com/lint-staged/lint-staged/commit/43a9b8d759443d3c313514b8a54af37108b19ac5";><code>43a9b8d</code></a> chore(changeset): release</li> <li><a href="https://github.com/lint-staged/lint-staged/commit/630e2f60abc9e3964cf62f3f833594a19cdaf3cd";><code>630e2f6</code></a> Merge pull request <a href="https://redirect.github.com/lint-staged/lint-staged/issues/1809";>#1809</a> from lint-staged/restore-merge-status</li> <li><a href="https://github.com/lint-staged/lint-staged/commit/179b4372b2528f6fa66f927337d238711694d0e0";><code>179b437</code></a> fix: restore Git merge status after creating backup stash</li> <li><a href="https://github.com/lint-staged/lint-staged/commit/6bae2e2aac7fd2981cf0b24e266631191760186c";><code>6bae2e2</code></a> Merge pull request <a href="https://redirect.github.com/lint-staged/lint-staged/issues/1811";>#1811</a> from lint-staged/exec-git-ignore-stderr</li> <li><a href="https://github.com/lint-staged/lint-staged/commit/b82a83099ddef36fccc26937761f184dfbe7c370";><code>b82a830</code></a> ci: run npm audit omitting dev, including prod dependencies</li> <li><a href="https://github.com/lint-staged/lint-staged/commit/0b19b80233efc83b8e7c6df3f117d87fe760752c";><code>0b19b80</code></a> build(deps): update dependencies</li> <li><a href="https://github.com/lint-staged/lint-staged/commit/3d0b2c0709a2a39aa7b134e3741fed21250d808e";><code>3d0b2c0</code></a> fix: ignore stderr when doing Git operations</li> <li><a href="https://github.com/lint-staged/lint-staged/commit/cd11fec419c59b4900aab194f288adf6bb4afdd1";><code>cd11fec</code></a> Merge pull request <a href="https://redirect.github.com/lint-staged/lint-staged/issues/1807";>#1807</a> from lint-staged/changeset-release/main</li> <li><a href="https://github.com/lint-staged/lint-staged/commit/15a8ee0df4ffb4c6fc65ea6828133cc32740c9c4";><code>15a8ee0</code></a> chore(changeset): release</li> <li>Additional commits viewable in <a href="https://github.com/lint-staged/lint-staged/compare/v16.4.0...v17.0.8";>compare view</a></li> </ul> </details> <br /> [](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 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> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
