Agent version update log #579
Open
Conversation
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
…er then the agent's version as it might break some experience
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
avaer
reviewed
Nov 19, 2024
| const agentSpecs = await parseAgentSpecs(args._[0]); | ||
|
|
||
| try { | ||
| await warnIfAgentsUseNewerSDKVersion(agentSpecs, opts); |
Contributor
There was a problem hiding this comment.
Probably shouldn't wait here as it will slow down the chat starting.
Contributor
There was a problem hiding this comment.
Maybe cache it for a period and don't do it during chat, but on any usdk command.
…nt-version-update-log
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.
This PR adds Agent version comparison with the current USDK version installed on the user's workstation.
Agent's created after a breaking change update to USDK would not work/cause unexpected behaviour with user's on a lower USDK version hence they need to be warned.