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/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.19",
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 to match langsmith version bump

The package.json changes langsmith from 0.3.73 to 0.5.19, but the pnpm-lock.yaml file was not updated — it still references langsmith@0.3.73 (see pnpm-lock.yaml:378-380). CI runs pnpm install --frozen-lockfile (.github/actions/pnpm-setup/action.yml:24), which will fail because the lockfile specifier (0.3.73) doesn't match the package.json specifier (0.5.19). This PR will break CI and cannot be installed correctly until pnpm install is re-run to regenerate the lockfile.

Prompt for agents
The package.json was updated to langsmith 0.5.19 but the pnpm-lock.yaml was not regenerated. Run `pnpm install` at the repo root to update the lockfile, then commit the updated pnpm-lock.yaml alongside this package.json change. Note that langsmith 0.5.x is a major jump from 0.3.x and may have breaking API changes — verify compatibility with the @langchain/* packages that depend on langsmith as a peer dependency (check pnpm-lock.yaml lines around 8410 and 19832 for the current langsmith resolution and its peer dependency constraints).
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