-
Notifications
You must be signed in to change notification settings - Fork 7
Add breaking change check for 0.0.154 #470
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.
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
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
Critical ordering issue: Place these entries after existing breaking changes.
The new
<0.0.154entries are positioned before older, more restrictive version constraints like<0.0.106and<0.0.115. SincecheckForBreakingChanges(line 231) stops at the first matching constraint, users on very old SDK versions (e.g., 0.0.100) will see only the telemetry update message and skip critical breaking changes that require code modifications (async AgentRequest signatures, API key environment variable changes, etc.). After updating to >=0.0.154, these older constraints will never trigger, leaving user code incompatible with the newer SDK.Move these two entries to the end of the
breakingChangesslice (after line 144, before the closing brace on line 145). This ensures users encounter breaking changes in chronological order, starting with the most restrictive (oldest) constraints first:var breakingChanges = []breakingChange{ - { - Runtime: "bunjs", - Version: "<0.0.154", - Title: "🚫 JS SDK Update Required 🚫", - Message: "An internal change related to telemetry requires updating to the latest SDK version. There are no code changes required on your end.\n\nPlease run bun update @agentuity/sdk --latest and then re-run this command again.", - }, - { - Runtime: "nodejs", - Version: "<0.0.154", - Title: "🚫 JS SDK Update Required 🚫", - Message: "An internal change related to telemetry requires updating to the latest SDK version. There are no code changes required on your end.\n\nPlease run npm upgrade @agentuity/sdk and then re-run this command again.", - }, { Runtime: "bunjs", Version: "<0.0.106",📝 Committable suggestion
🤖 Prompt for AI Agents