Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
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.jsonbumpslangsmithfrom0.3.73to0.5.18, but thepnpm-lock.yamlwas not updated and still contains onlylangsmith@0.3.73(withspecifier: 0.3.73for the agent package). There is nolangsmith@0.5.18entry in the lockfile at all. This mismatch will causepnpm install --frozen-lockfileto 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 byfrontend-ci.ymlbefore running lint and tests.Prompt for agents
Was this helpful? React with 👍 or 👎 to provide feedback.