Skip to content

deps: bump @eslint/js from 9.39.3 to 10.0.1 #68

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
fazxes merged 1 commit into from
Mar 2, 2026
Merged

deps: bump @eslint/js from 9.39.3 to 10.0.1 #68

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 @@ -147,7 +147,7 @@
"zustand": "^5.0.11"
},
"devDependencies": {
"@eslint/js": "^9.39.2",
"@eslint/js": "^10.0.1",

@chatgpt-codex-connector chatgpt-codex-connector Bot Feb 23, 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 lockfile alongside dependency range bump

package.json now requires @eslint/js ^10.0.1, but bun.lock still records @eslint/js as ^9.39.2 (see bun.lock:84), so the repo is left in an inconsistent state. Our CI jobs run bun install --frozen-lockfile (for example .github/workflows/ci.yml:34), and Bun documents that flag as Disallow changes to lockfile, which means installs will fail (or at minimum the intended upgrade will not be reproducible) until the lockfile is regenerated and committed.

Useful? React with 👍 / 👎.

"@tauri-apps/cli": "^2.10.0",
"@testing-library/jest-dom": "^6.9.1",
"@testing-library/react": "^16.3.2",
Expand Down
Loading