Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Bump lint-staged from 15.2.5 to 15.2.7 (#37)
Bumps [lint-staged](https://github.com/okonet/lint-staged) from 15.2.5 to 15.2.7. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/okonet/lint-staged/releases">lint-staged's releases</a>.</em></p> <blockquote> <h2>v15.2.7</h2> <h3>Patch Changes</h3> <ul> <li><a href="https://redirect.github.com/lint-staged/lint-staged/pull/1440">#1440</a> <a href="https://github.com/lint-staged/lint-staged/commit/a51be804b63307ac7af3c82f4cb2d43dbe92daac"><code>a51be80</code></a> Thanks <a href="https://github.com/iiroj"><code>@iiroj</code></a>! - In the previous version the native <code>git rev-parse --show-toplevel</code> command was taken into use for resolving the current git repo root. This version drops the <code>--path-format=absolute</code> option to support earlier git versions since it's also the default behavior. If you are still having trouble, please try upgrading <code>git</code> to the latest version.</li> </ul> <h2>v15.2.6</h2> <h3>Patch Changes</h3> <ul> <li><a href="https://redirect.github.com/lint-staged/lint-staged/pull/1433">#1433</a> <a href="https://github.com/lint-staged/lint-staged/commit/119adb29854cabddbfcf0469d7c8a0126184a5d4"><code>119adb2</code></a> Thanks <a href="https://github.com/iiroj"><code>@iiroj</code></a>! - Use native "git rev-parse" commands to determine git repo root directory and the .git config directory, instead of using custom logic. This hopefully makes path resolution more robust on non-POSIX systems.</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/lint-staged/lint-staged/blob/master/CHANGELOG.md">lint-staged's changelog</a>.</em></p> <blockquote> <h2>15.2.7</h2> <h3>Patch Changes</h3> <ul> <li><a href="https://redirect.github.com/lint-staged/lint-staged/pull/1440">#1440</a> <a href="https://github.com/lint-staged/lint-staged/commit/a51be804b63307ac7af3c82f4cb2d43dbe92daac"><code>a51be80</code></a> Thanks <a href="https://github.com/iiroj"><code>@iiroj</code></a>! - In the previous version the native <code>git rev-parse --show-toplevel</code> command was taken into use for resolving the current git repo root. This version drops the <code>--path-format=absolute</code> option to support earlier git versions since it's also the default behavior. If you are still having trouble, please try upgrading <code>git</code> to the latest version.</li> </ul> <h2>15.2.6</h2> <h3>Patch Changes</h3> <ul> <li><a href="https://redirect.github.com/lint-staged/lint-staged/pull/1433">#1433</a> <a href="https://github.com/lint-staged/lint-staged/commit/119adb29854cabddbfcf0469d7c8a0126184a5d4"><code>119adb2</code></a> Thanks <a href="https://github.com/iiroj"><code>@iiroj</code></a>! - Use native "git rev-parse" commands to determine git repo root directory and the .git config directory, instead of using custom logic. This hopefully makes path resolution more robust on non-POSIX systems.</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/lint-staged/lint-staged/commit/87e4b30bd6ff967d391e9cf84eac8387636af7ad"><code>87e4b30</code></a> chore(changeset): release (<a href="https://redirect.github.com/okonet/lint-staged/issues/1441">#1441</a>)</li> <li><a href="https://github.com/lint-staged/lint-staged/commit/a39e8291d173e2357a84abeee63638eb9182bf16"><code>a39e829</code></a> docs: adjust changeset</li> <li><a href="https://github.com/lint-staged/lint-staged/commit/a51be804b63307ac7af3c82f4cb2d43dbe92daac"><code>a51be80</code></a> fix: drop option to support earlier Git versions</li> <li><a href="https://github.com/lint-staged/lint-staged/commit/a91d942930672fce37de639cef49949b08b522da"><code>a91d942</code></a> chore(changeset): release</li> <li><a href="https://github.com/lint-staged/lint-staged/commit/119adb29854cabddbfcf0469d7c8a0126184a5d4"><code>119adb2</code></a> fix: use native git command to get .git directory</li> <li><a href="https://github.com/lint-staged/lint-staged/commit/e0386dc1a9e545df49f246b0e14476ea3fb8dcb2"><code>e0386dc</code></a> fix: use native git command to get top-level directory for repo</li> <li><a href="https://github.com/lint-staged/lint-staged/commit/659387011754eeed818646ce594a772f3106e49a"><code>6593870</code></a> ci: test Node.js versions against current instead of latest dependency</li> <li><a href="https://github.com/lint-staged/lint-staged/commit/6c226c52b6b8a28429026aee93b828c1e5775238"><code>6c226c5</code></a> ci: add workflow for testing required Node.js semver range</li> <li>See full diff in <a href="https://github.com/okonet/lint-staged/compare/v15.2.5...v15.2.7">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.2.5&new-version=15.2.7)](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>
- Loading branch information