Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
adm01-debug merged 1 commit into from
May 12, 2026
Merged

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

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
81 changes: 48 additions & 33 deletions package-lock.json
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -140,7 +140,7 @@
"jsdom": "^20.0.3",
"jspdf": "4.2.1",
"jspdf-autotable": "5.0.7",
"lint-staged": "^16.4.0",
"lint-staged": "^17.0.4",
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot May 11, 2026

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.

"lovable-tagger": "^1.1.13",
"lucide-react": "^0.309.0",
"otpauth": "^9.2.2",
Expand Down
Loading