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 frontend/packages/schema/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@
"neverthrow": "8.2.0",
"pg-query-emscripten": "5.1.0",
"valibot": "1.1.0",
"yaml": "2.8.1",
"yaml": "2.8.3",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

🔴 Lockfile not updated to match package.json version bump, will break CI

The package.json specifies "yaml": "2.8.3" but pnpm-lock.yaml still records specifier: 2.8.1 and version: 2.8.1 (at pnpm-lock.yaml:978-980). Since CI runs pnpm install --frozen-lockfile (.github/actions/pnpm-setup/action.yml:24), this mismatch will cause the install step to fail with an error about the lockfile being out of date.

Prompt for agents
Run `pnpm install` to regenerate the lockfile so that pnpm-lock.yaml reflects the updated yaml version 2.8.3 specified in frontend/packages/schema/package.json line 26. The lockfile at pnpm-lock.yaml lines 978-980 currently still references yaml 2.8.1. After running pnpm install, commit the updated pnpm-lock.yaml.
Open in Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

"zod": "4.0.0"
},
"devDependencies": {
Expand Down
Loading