Skip to content
Open
Changes from all commits
Commits
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 packages/junior/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -106,7 +106,7 @@
"devDependencies": {
"@emnapi/core": "^1.10.0",
"@emnapi/runtime": "^1.10.0",
"@hono/node-server": "1.19.14",
"@hono/node-server": "1.19.15",

Check warning on line 109 in packages/junior/package.json

View check run for this annotation

@sentry/warden / warden: code-review

Dependency bump leaves pnpm-lock.yaml pinned to @hono/node-server 1.19.14

`packages/junior/package.json` requires `@hono/node-server` 1.19.15, but the lockfile still records 1.19.14. Any CI job running the repository's frozen pnpm install will fail before tests or builds run, blocking the dependency update and release artifact workflow.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Incomplete dependency lockfile update

High Severity

@hono/node-server is bumped to 1.19.15 in packages/junior/package.json, but pnpm-lock.yaml still pins specifier and resolution to 1.19.14. CI installs with pnpm install --frozen-lockfile, so the mismatch fails dependency install before any tests run and the bump never takes effect.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 9077b1f. Configure here.

"@oxlint/plugins": "1.79.0",
"@sentry/junior-github": "workspace:*",
"@sentry/junior-memory": "workspace:*",
Expand Down
Loading