Skip to content

build(deps-dev): bump lint-staged from 16.4.0 to 17.0.8 #22

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

Open
dependabot wants to merge 1 commit into
base: main
Choose a base branch
from
Open

build(deps-dev): bump lint-staged from 16.4.0 to 17.0.8 #22

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
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 @@ -74,7 +74,7 @@
"concurrently": "^9.2.1",
"drizzle-kit": "^0.31.9",
"husky": "^9.1.7",
"lint-staged": "^16.3.0",
"lint-staged": "^17.0.8",

@chatgpt-codex-connector chatgpt-codex-connector Bot Jul 1, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Update bun.lock with the dependency bump

This change updates the manifest to lint-staged@^17.0.8 but leaves the committed bun.lock resolving the root devDependency as ^16.3.0 / lint-staged@16.4.0. The Docker build copies package.json bun.lock and runs bun install --frozen-lockfile (docker/Dockerfile lines 8-11), and the installer does the same (install.sh line 1250); bun install --help describes --frozen-lockfile as disallowing lockfile changes, so these install paths need the lockfile updated in the same commit rather than trying to resolve a new package version during a frozen install.

Useful? React with 👍 / 👎.

"vite": "^7.3.1"
},
"peerDependencies": {
Expand Down
Loading