#1840efe5b63 - This is a version-bump-only release because the previous version 17.4.0 was not published to npmjs.com due to problems with GitHub Actions and Changesets.
17.4.0
Minor Changes
#183690ec282 - Added a new defineConfig helper for type-checking the lint-staged configuration:
#1832510a27c - Added a new flag --all to make lint-staged include all files tracked by Git, instead of only staged.
By default lint-staged only runs tasks on files that include staged changes (hence the name). Use this flag to include all files tracked in Git version control (standard exclusions apply). Using this flag implies the --no-stash flag, disabling the automatic backup, and the --allow-empty flag so that lint-staged doesn't fail when there are no changes after running. This makes it easier to run npx lint-staged --all on a clean state, for example in CI.
Patch Changes
#183869bec99 - The behavior of the automatic backup stash has been improved when running lint-staged in multiple worktrees in parallel. You should still avoid running multiple instances of lint-staged in parallel in the same tree, because some of the Git operations are locking and might lead to data loss.
#18395e5bdd2 - Parsing of lint-staged CLI flags and Node.js API options has been rewritten to avoid inconsistent behavior between the two.
<h1>npm</h1>
<h2>lint-staged</h2>
<ul>
<li> ^17.3.0 => ^17.4.1 (vscodestat)</li>
</ul>
> <h2>17.4.1</h2>
> <h3>Patch Changes</h3>
> <ul>
> <li><a href="https://github.com/lint-staged/lint-staged/pull/1840">#1840</a> <a href="https://github.com/lint-staged/lint-staged/commit/efe5b63cc4961c80b6363fe40bac3c145e3ddbb2"><code>efe5b63</code></a> - This is a version-bump-only release because the previous version <code>17.4.0</code> was not published to npmjs.com due to problems with GitHub Actions and Changesets.</li>
> </ul>
> <h2>17.4.0</h2>
> <h3>Minor Changes</h3>
> <ul>
> <li><p><a href="https://github.com/lint-staged/lint-staged/pull/1836">#1836</a> <a href="https://github.com/lint-staged/lint-staged/commit/90ec28245085343f56661ebc004e7b89304762dd"><code>90ec282</code></a> - Added a new <code>defineConfig</code> helper for type-checking the <em>lint-staged</em> configuration:</p>
> <pre><code class="language-ts">// lint-staged.config.ts
> import { defineConfig } from 'lint-staged/config'
> export default defineConfig({
> '*.js': ['prettier --check', 'eslint'],
> })
> </code></pre>
> </li>
> <li><p><a href="https://github.com/lint-staged/lint-staged/pull/1832">#1832</a> <a href="https://github.com/lint-staged/lint-staged/commit/510a27cac303990d71755aec203caed605b53caa"><code>510a27c</code></a> - Added a new flag <code>--all</code> to make <em>lint-staged</em> include all files tracked by Git, instead of only staged.</p>
> <p>By default <em>lint-staged</em> only runs tasks on files that include staged changes (hence the name). Use this flag to include all files tracked in Git version control (standard exclusions apply). Using this flag implies the <code>--no-stash</code> flag, disabling the automatic backup, and the <code>--allow-empty</code> flag so that <em>lint-staged</em> doesn't fail when there are no changes after running. This makes it easier to run <code>npx lint-staged --all</code> on a clean state, for example in CI.</p>
> </li>
> </ul>
> <h3>Patch Changes</h3>
> <ul>
> <li><p><a href="https://github.com/lint-staged/lint-staged/pull/1838">#1838</a> <a href="https://github.com/lint-staged/lint-staged/commit/69bec9930a73901bf908e3d0c0cdcafe5abf74b1"><code>69bec99</code></a> - The behavior of the automatic backup stash has been improved when running <em>lint-staged</em> in multiple worktrees in parallel. You should still avoid running multiple instances of <em>lint-staged</em> in parallel in the same tree, because some of the Git operations are locking and might lead to data loss.</p>
> </li>
> <li><p><a href="https://github.com/lint-staged/lint-staged/pull/1839">#1839</a> <a href="https://github.com/lint-staged/lint-staged/commit/5e5bdd29645063300256109bbbceb9dabcb014e4"><code>5e5bdd2</code></a> - Parsing of <em>lint-staged</em> CLI flags and Node.js API options has been rewritten to avoid inconsistent behavior between the two.</p>
> </li>
> </ul>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
npm
lint-staged