Skip to content
Closed
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/internal-packages/agent/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@
"@valibot/to-json-schema": "1.3.0",
"dotenv": "16.5.0",
"fast-json-patch": "3.1.1",
"langsmith": "0.3.73",
"langsmith": "0.5.18",
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.

🔴 pnpm-lock.yaml not updated after langsmith version bump

The package.json bumps langsmith from 0.3.73 to 0.5.18, but the pnpm-lock.yaml was not updated and still contains only langsmith@0.3.73 (with specifier: 0.3.73 for the agent package). There is no langsmith@0.5.18 entry in the lockfile at all. This mismatch will cause pnpm install --frozen-lockfile to fail in CI, and without --frozen-lockfile, the lockfile would be silently rewritten, defeating its purpose. The CI setup action (.github/actions/pnpm-setup/action.yml) is used by frontend-ci.yml before running lint and tests.

Prompt for agents
The pnpm-lock.yaml file was not updated to reflect the langsmith version change from 0.3.73 to 0.5.18 in frontend/internal-packages/agent/package.json. Run `pnpm install` at the repo root to regenerate the lockfile, which will add a langsmith@0.5.18 resolution entry and update the specifier for the agent package from 0.3.73 to 0.5.18. Then commit the updated pnpm-lock.yaml alongside the package.json change.
Open in Devin Review

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

"neverthrow": "8.2.0",
"uuid": "11.1.0",
"valibot": "1.1.0"
Expand Down
Loading