---
title: "lint-staged 17.6.1: release notes, upgrades and advisories"
description: "lint-staged 17.6.1: release notes, breaking changes by major version and no known security advisory."
url: https://inlinr.com/packages/lint-staged
lang: en
---

[Packages](https://inlinr.com/packages)

# lint-staged

17.6.1 · 15 Nov 2026 MIT 42.2M / week [Repository](https://github.com/lint-staged/lint-staged) [Homepage](https://github.com/lint-staged/lint-staged#readme) [npm](https://www.npmjs.com/package/lint-staged) [Atom feed](https://inlinr.com/packages/feed/lint-staged)

Your version 

## Where each line stands

[Plan an upgrade](https://inlinr.com/packages/lint-staged/upgrade)

LineNewestSecurity

- 17.x 17.6.1 No known advisory Latest line
- 16.x 16.4.0 No known advisory [To 17.6.1](https://inlinr.com/packages/lint-staged/upgrade/16.4.0-17.6.1)
- 15.x 15.5.2 No known advisory [To 17.6.1](https://inlinr.com/packages/lint-staged/upgrade/15.5.2-17.6.1)
- 14.x 14.0.1 No known advisory [To 17.6.1](https://inlinr.com/packages/lint-staged/upgrade/14.0.1-17.6.1)
- 13.x 13.3.0 No known advisory [To 17.6.1](https://inlinr.com/packages/lint-staged/upgrade/13.3.0-17.6.1)
- 12.x 12.5.0 No known advisory [To 17.6.1](https://inlinr.com/packages/lint-staged/upgrade/12.5.0-17.6.1)

## What to use instead

## A better maintained package

From the [e18e module-replacements](https://github.com/es-tooling/module-replacements) list, maintained by the community.

The list compares the options for lint-staged: [read the comparison](https://github.com/es-tooling/module-replacements/blob/main/docs/modules/lint-staged.md).

## Before you switch

1. 1  
Check what else depends on it  
Paste your package.json in the [dependency check](https://inlinr.com/tools/dependency-check) to see every deprecated or outdated package in one pass, not only this one.
2. 2  
Read the replacement's peers and releases  
A native API or a few lines of code need no release notes, but check the Node version your project runs on.
3. 3  
Know when it ships  
Follow the new package on inlinr: its releases and advisories land in your feed, and the time spent on the migration branch shows on its page.

## Latest releases

[All 269 releases](https://inlinr.com/packages/lint-staged/releases)

1. 17.x · latest line
2. ### [17.6.1](https://inlinr.com/packages/lint-staged/releases/17.6.1 "Open this release") [](https://github.com/lint-staged/lint-staged/releases/tag/v17.6.1 "Read this release where it was published")  
15 Nov 2026

  - The warning about the temporary patch file containing hidden partially-staged changes is only displayed when restoring the changes failed.
3. ### [17.6.0](https://inlinr.com/packages/lint-staged/releases/17.6.0 "Open this release") [](https://github.com/lint-staged/lint-staged/blob/HEAD/CHANGELOG.md "Read this release where it was published")  
26 Sep 2026

  - Task functions like `{ title, task }` can now use a logger function `log()` to emit output while the task runs. By default, the output will only be visible if the task fails, unless the `--verbose` option was used. Additionally, when the task rejects, the error will be shown in the output.  
  ```
  import { defineConfig } from 'lint-staged/config'
  export default defineConfig({
    '*': {
      title: 'Fail if PDF files are committed',
      task: async (filepaths, { log }) => {
        const pdfFiles = filepaths.filter((f) => f.toLowerCase().endsWith('.pdf'))
        if (pdfFiles.length > 0) {
          log('PDF files should not be committed: %s', pdfFiles)
          throw new Error('Failed')
        }
      },
    },
  })
  ```
  - _lint-staged_ now stages changes to **all tracked files modified by tasks**, including files that weren’t originally staged or didn’t match the configured globs. This can happen when your task has side-effects, or it's a function that ignores the staged files like `() => "prettier --write ."`.  
  If you have unstaged changes in a file and the task also edits that file, your unstaged changes will be staged too. Use `--hide-unstaged` to hide your changes while tasks run.
  - The assignment of staged files to _lint-staged_ configuration files (when using multiple, for example in a monorepo) has been rewritten to be more efficient. As a reminder, each staged file is assigned to exactly one configuration (the closest one), even if that config doesn't match the file in its globs.
4. ### [17.5.1](https://inlinr.com/packages/lint-staged/releases/17.5.1 "Open this release") [](https://github.com/lint-staged/lint-staged/blob/HEAD/CHANGELOG.md "Read this release where it was published")  
10 Sep 2026

  - Fix TypeScript issue `TS1254` from `defineConfig()` by changing the signature from `const` to a `function`:  
  > A 'const' initializer in an ambient context must be a string or numeric literal or literal enum reference.

Dependency tracking

## Know when your own dependencies move

lint-staged shipped a new major in the last 12 months, among 24 releases. inlinr shows which of your projects are behind, and what the upgrade breaks.

- Advisories reach you  
An email when a critical or high advisory affects a project, before the next install.
- Upgrades checked first  
Peer ranges, Node, ESM-only and types changes read before you bump.
- Only what matters  
Majors and breaking notes stay; patches and sibling bumps fold into one line.

[How dependency tracking works](https://inlinr.com/dependencies)

## Security

No known security advisory.

## Health of 17.6.1

[Details](https://inlinr.com/packages/lint-staged/security#signals)

- **Provenance**: Present
- **Publisher**: GitHub Actions
- **Maintainers**: 2
- **Scorecard**: None
- **Size**: 168 kB

## Weekly downloads

Reading releases, release notes and advisories…

Registry facts last checked 18 Nov 2026\. Releases and advisories last read 19 Nov 2026.

A whole project to check? Paste its package.json in the [dependency check](https://inlinr.com/tools/dependency-check): every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.
