Bump langsmith from 0.3.73 to 0.5.18 in /frontend/internal-packages/schema-bench#4077
Conversation
Bumps [langsmith](https://github.com/langchain-ai/langsmith-sdk) from 0.3.73 to 0.5.18. - [Release notes](https://github.com/langchain-ai/langsmith-sdk/releases) - [Commits](https://github.com/langchain-ai/langsmith-sdk/commits) --- updated-dependencies: - dependency-name: langsmith dependency-version: 0.5.18 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
|
Finished running flow.
|
||||||||||||
|
The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
|
Check changeset necessityStatus: NOT REQUIRED Reason:
Changeset (copy & paste):<!-- No changeset required: dependency update in ignored package @liam-hq/schema-bench --> |
| "@liam-hq/schema": "workspace:*", | ||
| "dotenv": "16.5.0", | ||
| "langsmith": "0.3.73", | ||
| "langsmith": "0.5.18", |
There was a problem hiding this comment.
🔴 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 — it still references specifier: 0.3.73 for both the schema-bench and agent packages. Running pnpm install --frozen-lockfile (as CI typically does) will fail because the lockfile is out of sync with package.json. This is a major semver jump (0.3 → 0.5) that also likely involves breaking API changes to imports like evaluate from langsmith/evaluation, Client from langsmith, EvaluatorT from langsmith/evaluation, and Run/Example from langsmith/schemas (used in frontend/internal-packages/schema-bench/src/langsmith/schemaEvaluator.ts:2-3 and frontend/internal-packages/schema-bench/src/cli/evaluateWithLangsmith.ts:6).
Prompt for agents
The pnpm-lock.yaml file was not regenerated after bumping langsmith from 0.3.73 to 0.5.18 in frontend/internal-packages/schema-bench/package.json. This will cause CI failures when running pnpm install --frozen-lockfile. Run pnpm install to regenerate the lockfile and commit the updated pnpm-lock.yaml. Additionally, since this is a major version jump (0.3 to 0.5), verify that the langsmith API is still compatible with the current usage: evaluate from langsmith/evaluation, Client from langsmith, EvaluatorT from langsmith/evaluation, and Run/Example from langsmith/schemas (used in schemaEvaluator.ts and evaluateWithLangsmith.ts and uploadDatasetToLangsmith.ts). Check the langsmith changelog for breaking changes between 0.3 and 0.5.
Was this helpful? React with 👍 or 👎 to provide feedback.
|
Superseded by #4083. |
Bumps langsmith from 0.3.73 to 0.5.18.
Release notes
Sourced from langsmith's releases.
... (truncated)
Commits
Maintainer changes
This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for langsmith since your current version.
Install script changes
This version modifies
prepublishscript that runs during installation. Review the package contents before updating.Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.