Skip to content

deps(npm): bump chromedriver from 145.0.6 to 146.0.1 in /frontend #19

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

Closed
dependabot wants to merge 1 commit into from
Closed

deps(npm): bump chromedriver from 145.0.6 to 146.0.1 in /frontend #19

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 frontend/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@
"@types/react-dom": "^19.2.3",
"@types/uuid": "^11.0.0",
"@vitest/coverage-v8": "^4.0.17",
"chromedriver": "145",
"chromedriver": "146",
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector bot Mar 9, 2026

Choose a reason for hiding this comment

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

P1 Badge Update lockfile for chromedriver bump

This change bumps chromedriver in package.json to 146 but leaves frontend/bun.lock pinned to 145.0.6, which makes the dependency graph inconsistent. In this repo, CI installs with bun install --frozen-lockfile (see .github/workflows/ci-cd.yml), and bun install --help states this flag will "Disallow changes to lockfile," so the frontend install step will fail until the lockfile is regenerated and committed alongside this version bump.

Useful? React with 👍 / 👎.

"eslint": "^10.0.0",
"eslint-plugin-react-hooks": "^7.0.1",
"eslint-plugin-react-refresh": "^0.5.0",
Expand Down
Loading