Skip to content

chore(deps)(deps): bump lint-staged from 16.4.0 to 17.0.4#139

Merged
adm01-debug merged 1 commit into
mainfrom
dependabot/npm_and_yarn/lint-staged-17.0.4
May 12, 2026
Merged

chore(deps)(deps): bump lint-staged from 16.4.0 to 17.0.4#139
adm01-debug merged 1 commit into
mainfrom
dependabot/npm_and_yarn/lint-staged-17.0.4

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot Bot commented on behalf of github May 11, 2026

Bumps lint-staged from 16.4.0 to 17.0.4.

Release notes

Sourced from lint-staged's releases.

v17.0.4

Patch Changes

  • #1788 f95c1f8 - Another fix for making sure lint-staged adds task modifications correctly to the commit in the following cases:

    • after editing <file> it is staged with git add <file>, and then committed with git commit
    • after editing <file> it is committed with git commit --all without explicit git add
    • after editing <file> it is committed with git commit <pathspec> without explicit git add

    There's new test cases which actually setup the Git pre_commit hook to run lint-staged and verify them. These issues started in v17.0.0 when trying to improve support for committig without having explicitly staged files.

v17.0.3

Patch Changes

  • #1782 06813f9 Thanks @​iiroj! - Fix lint-staged behavior when implicitly committing files without using git add by either:
    • git commit -am "my commit message" where -a (--all) means to automatically stage all tracked modified and deleted files
    • git commit -m "my commit message" . where . is an example of a pathspec where matching files will be staged

v17.0.2

Patch Changes

v17.0.1

Patch Changes

  • #1776 4a5664b Thanks @​iiroj! - Adjust GitHub Actions workflow so that automatic publishing works with signed commits.

v17.0.0

Major Changes

  • #1745 e244adf Thanks @​iiroj! - Node.js v20 is no longer supported, and the oldest supported version is now 22.22.1, which is an active LTS version at the time of this release. Node.js 20 will be EOL after April 2026. Please upgrade your Node.js version!

  • #1676 0584e0b Thanks @​outslept! - Lint-staged now tries to verify the installed Git version is at least 2.32.0, released in 2021. If you're using an even older Git version, you need to upgrade it before running lint-staged!

  • #1745 2dcc40a Thanks @​iiroj! - The dependency yaml is now marked as optional and probably won't be installed by default. If you're using a YAML configuration file you should install the package separately:

    npm install --development yaml

    If you're using .lintstagedrc as the config file name (without a file extension), it will be treated as a YAML file. If the content is JSON, consider renaming it to .lintstagedrc.json to avoid needing to install yaml.

Minor Changes

  • #1748 809d5ef Thanks @​iiroj! - Add new option --hide-all for hiding all unstaged changes and untracked files, before running tasks. This makes it easier to run tools like Knip which check for unused code. Untracked files are included in the backup stash and restored automatically after running.

  • #1759 f13045a Thanks @​iiroj! - Update dependencies, including tinyexec@1.1.1 to fix the following issues:

    • When using a Node.js version manager with multiple versions installed (nvm, n, for example), scripts with the #!/usr/bin/env node shebang (Prettier, ESLint, for example) were previously spawned using the default Node.js version configured by the version manager (the one which node points to) on POSIX systems. Now, they will be spawned with the same version that lint-staged itself was started with.
      • For example, if your default Node.js version is 24.14.1 but lint-staged is run with the latest version 25.9.0, the tasks spawned by lint-staged will now also use version 25.9.0. Previously they were spawned using 24.14.1.

... (truncated)

Changelog

Sourced from lint-staged's changelog.

17.0.4

Patch Changes

  • #1788 f95c1f8 - Another fix for making sure lint-staged adds task modifications correctly to the commit in the following cases:

    • after editing <file> it is staged with git add <file>, and then committed with git commit
    • after editing <file> it is committed with git commit --all without explicit git add
    • after editing <file> it is committed with git commit <pathspec> without explicit git add

    There's new test cases which actually setup the Git pre_commit hook to run lint-staged and verify them. These issues started in v17.0.0 when trying to improve support for committig without having explicitly staged files.

17.0.3

Patch Changes

  • #1782 06813f9 Thanks @​iiroj! - Fix lint-staged behavior when implicitly committing files without using git add by either:
    • git commit -am "my commit message" where -a (--all) means to automatically stage all tracked modified and deleted files
    • git commit -m "my commit message" . where . is an example of a pathspec where matching files will be staged

17.0.2

Patch Changes

17.0.1

Patch Changes

  • #1776 4a5664b Thanks @​iiroj! - Adjust GitHub Actions workflow so that automatic publishing works with signed commits.

17.0.0

Major Changes

  • #1745 e244adf Thanks @​iiroj! - Node.js v20 is no longer supported, and the oldest supported version is now 22.22.1, which is an active LTS version at the time of this release. Node.js 20 will be EOL after April 2026. Please upgrade your Node.js version!

  • #1676 0584e0b Thanks @​outslept! - Lint-staged now tries to verify the installed Git version is at least 2.32.0, released in 2021. If you're using an even older Git version, you need to upgrade it before running lint-staged!

  • #1745 2dcc40a Thanks @​iiroj! - The dependency yaml is now marked as optional and probably won't be installed by default. If you're using a YAML configuration file you should install the package separately:

    npm install --development yaml

    If you're using .lintstagedrc as the config file name (without a file extension), it will be treated as a YAML file. If the content is JSON, consider renaming it to .lintstagedrc.json to avoid needing to install yaml.

Minor Changes

  • #1748 809d5ef Thanks @​iiroj! - Add new option --hide-all for hiding all unstaged changes and untracked files, before running tasks. This makes it easier to run tools like Knip which check for unused code. Untracked files are included in the backup stash and restored automatically after running.

... (truncated)

Commits
  • 2862964 Merge pull request #1789 from lint-staged/changeset-release/main
  • c9ecd54 chore(changeset): release
  • cc6b51a Merge pull request #1788 from lint-staged/fix-update-index-again
  • f95c1f8 fix: update both default index.lock and non-standard lock when latter exists
  • f44ee68 Merge pull request #1786 from lint-staged/update-repo-url
  • a61cf18 build(deps): update dependencies
  • ea00037 docs: disable Changesets "thanks"
  • ab7c26c docs: update repo URL to point in lint-staged/lint-staged
  • a36ec1e Merge pull request #1783 from lint-staged/changeset-release/main
  • 03ce2a9 chore(changeset): release
  • Additional commits viewable in compare view

Summary by CodeRabbit

Chores

  • Atualizada a dependência lint-staged para a versão mais recente.

Review Change Stack

@dependabot @github
Copy link
Copy Markdown
Contributor Author

dependabot Bot commented on behalf of github May 11, 2026

Labels

The following labels could not be found: automated, dependencies. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

@dependabot dependabot Bot requested a review from adm01-debug as a code owner May 11, 2026 13:08
@vercel
Copy link
Copy Markdown

vercel Bot commented May 11, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
promo-gifts Ready Ready Preview, Comment May 12, 2026 5:49pm

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 11, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 95860251-813c-43cb-9a5e-b93b41dfcf3b

📥 Commits

Reviewing files that changed from the base of the PR and between 31a6049 and 6c9fc56.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json, !**/package-lock.json
📒 Files selected for processing (1)
  • package.json
🚧 Files skipped from review as they are similar to previous changes (1)
  • package.json

Walkthrough

Atualização do package.json: dependência lint-staged elevada de ^16.4.0 para ^17.0.4. Nenhuma outra alteração em scripts, configurações ou dependências.

Changes

Atualização de Dependência

Layer / File(s) Summary
Versão lint-staged
package.json
Dependência lint-staged atualizada de ^16.4.0 para ^17.0.4.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested reviewers

  • adm01-debug
🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning A descrição não segue o template obrigatório do repositório (português). Faltam seções críticas como Tipo de Mudança, Checklist e validações de segurança/compatibilidade. Adicione seções do template: marque 'chore' em Tipo de Mudança, confirme Node.js 22.22.1+, teste lint-staged e documnte breaking changes (Node v20 não suportado, yaml opcional).
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed O título descreve com clareza a mudança principal: atualização do lint-staged de 16.4.0 para 17.0.4, alinhado com o conteúdo do PR.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch dependabot/npm_and_yarn/lint-staged-17.0.4

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@package.json`:
- Line 143: O package.json atual atualizou "lint-staged" para 17.x, que requer
Node >= 22.22.1 e Git >= 2.32.0 enquanto o projeto ainda declara "node":
">=20.0.0", fazendo falhar hooks/CI; reverta a dependência "lint-staged" para a
faixa compatível com Node 20 (por exemplo "lint-staged": "16.x") no package.json
e/ou atualize a chave "engines" para refletir o requisito mínimo real se for
aceitável elevar suporte a Node, garantindo também que
documentação/CI/pre-commit apontem a versão mínima de Git se necessário.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: be42e03a-bd1f-4b09-b6ce-25dae31ae867

📥 Commits

Reviewing files that changed from the base of the PR and between dfd0384 and 31a6049.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json, !**/package-lock.json
📒 Files selected for processing (1)
  • package.json

Comment thread package.json
"jspdf": "4.2.1",
"jspdf-autotable": "5.0.7",
"lint-staged": "^16.4.0",
"lint-staged": "^17.0.4",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major | 🏗️ Heavy lift

🧩 Analysis chain

🌐 Web query:

lint-staged 17.0 Node.js version requirements breaking changes

💡 Result:

For lint-staged 17.0.0, the Node.js version requirements breaking change is: Node.js v20 is no longer supported, and the oldest supported version is Node.js 22.22.1 (active v22 LTS at the time of the release). [1][2] What to do (breaking impact): - If your pre-commit/CI runs lint-staged with Node.js 20, upgrade the runtime to at least Node.js 22.22.1 (or newer, e.g., v24/v25). [2][1] Additional related breaking/support changes in the same v17.0.0 release: - lint-staged now requires/validates Git version >= 2.32.0; if you use an older Git, you must upgrade before running lint-staged. [1][3] Evidence: lint-staged’s v17 migration notes explicitly state the Node.js v20 removal and the new minimum (22.22.1), and the v17.0.0 release notes repeat that Node.js v20 is no longer supported. [2][1]

Citations:


🏁 Script executed:

cat package.json | grep -A 5 "lint-staged\|engines"

Repository: adm01-debug/Promo_Gifts

Length of output: 452


lint-staged@17 quebra com Node 20 declarado em engines

Esse bump exige Node >= 22.22.1, mas o projeto ainda declara "node": ">=20.0.0". Pre-commit hooks e CI vão falhar na execução.

Além disso, lint-staged@17 também passou a exigir Git >= 2.32.0.

💡 Ajuste necessário
   "engines": {
-    "node": ">=20.0.0",
+    "node": ">=22.22.1",
     "npm": ">=10.0.0"
   }

Se o projeto ainda precisa suportar Node 20, recue lint-staged para 16.x.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@package.json` at line 143, O package.json atual atualizou "lint-staged" para
17.x, que requer Node >= 22.22.1 e Git >= 2.32.0 enquanto o projeto ainda
declara "node": ">=20.0.0", fazendo falhar hooks/CI; reverta a dependência
"lint-staged" para a faixa compatível com Node 20 (por exemplo "lint-staged":
"16.x") no package.json e/ou atualize a chave "engines" para refletir o
requisito mínimo real se for aceitável elevar suporte a Node, garantindo também
que documentação/CI/pre-commit apontem a versão mínima de Git se necessário.

@adm01-debug
Copy link
Copy Markdown
Owner

@dependabot rebase

Bumps [lint-staged](https://github.com/lint-staged/lint-staged) from 16.4.0 to 17.0.4.
- [Release notes](https://github.com/lint-staged/lint-staged/releases)
- [Changelog](https://github.com/lint-staged/lint-staged/blob/main/CHANGELOG.md)
- [Commits](lint-staged/lint-staged@v16.4.0...v17.0.4)

---
updated-dependencies:
- dependency-name: lint-staged
  dependency-version: 17.0.4
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot force-pushed the dependabot/npm_and_yarn/lint-staged-17.0.4 branch from 31a6049 to 6c9fc56 Compare May 12, 2026 17:48
@adm01-debug adm01-debug merged commit 85a309c into main May 12, 2026
13 of 14 checks passed
@dependabot dependabot Bot deleted the dependabot/npm_and_yarn/lint-staged-17.0.4 branch May 12, 2026 17:58
adm01-debug added a commit that referenced this pull request May 12, 2026
Tarefa 7 do redeploy. Triagei 7 PRs dependabot abertas há semanas.

Resultado:
- 4 mergeadas: #138, #139, #144, #145 (devtools + CI actions, baixo risco)
- 3 fechadas: #140, #141, #142 (runtime majors com breaking changes)
- 1 issue criada: #155 (tracking dos 3 majors pendentes)

Critério: triagem por RISCO REAL (devtools vs runtime), não por minor/major.

Decisões persistidas em docs/redeploy/REDEPLOY-T7-DEPENDABOT.md:
- Lista completa das 7 PRs com decisão e razão
- Critérios de triagem reutilizáveis
- Achados sobre falsos-positivos (CDN 522 do esm.sh)
- Recomendação de dependabot.yml para reduzir ruído futuro
- Status atualizado do plano de redeploy

Closes part of #155 (T7 do plano)

Co-authored-by: Joaquim (via Claude Code redeploy T2) <joaquim@atomicabr.com.br>
Co-authored-by: Claude <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant