Skip to content

Bump langsmith from 0.3.73 to 0.5.19 in /frontend/internal-packages/schema-bench #4083

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

Open
dependabot wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Bump langsmith from 0.3.73 to 0.5.19 in /frontend/internal-packages/schema-bench #4083

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/internal-packages/schema-bench/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@
"@liam-hq/neverthrow": "workspace:*",
"@liam-hq/schema": "workspace:*",
"dotenv": "16.5.0",
"langsmith": "0.3.73",
"langsmith": "0.5.19",
Copy link
Copy Markdown
Contributor

@devin-ai-integration devin-ai-integration Bot Apr 16, 2026

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 package.json version bump

The package.json bumps langsmith from 0.3.73 to 0.5.19, but the pnpm-lock.yaml still records specifier: 0.3.73 for the schema-bench package (pnpm-lock.yaml:670-672). This mismatch means pnpm install --frozen-lockfile (the default behavior in CI when CI=true) will fail because the lockfile specifier doesn't match the package.json requirement. The lockfile must be regenerated by running pnpm install and committing the updated pnpm-lock.yaml.

Prompt for agents 
The package.json was updated to langsmith 0.5.19 but pnpm-lock.yaml was not regenerated. At pnpm-lock.yaml:670-672, the specifier still reads 0.3.73. Run `pnpm install` at the repo root to regenerate the lockfile, then commit the updated pnpm-lock.yaml alongside this package.json change. Without this, CI will fail when running pnpm install with frozen lockfile.
Open in Devin Review

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

"neverthrow": "8.2.0",
"openai": "5.9.2",
"tsx": "4.20.6",
Expand Down
Loading