Bump langsmith from 0.3.73 to 0.5.18 in /frontend/internal-packages/agent#4078
Closed
dependabot[bot] wants to merge 1 commit intomainfrom
Closed
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>
dependabot
Bot
added
dependencies
dependabot
Bot
requested review from
NoritakaIkeda and
sasamuku
and removed request for
a team
dependabot
Bot
added
dependencies
|
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 for this PR because it only affects "@liam-hq/agent" (ignored package). |
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
| "dotenv": "16.5.0", | ||
| "fast-json-patch": "3.1.1", | ||
| "langsmith": "0.3.73", | ||
| "langsmith": "0.5.18", |
Contributor
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 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.
Was this helpful? React with 👍 or 👎 to provide feedback.
Contributor
Author
|
Superseded by #4082. |
dependabot
Bot
deleted the
dependabot/npm_and_yarn/frontend/internal-packages/agent/langsmith-0.5.18
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
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.