Skip to content

Conversation

@julianduque
Copy link
Owner

Migrate to ai-sdk v5

@julianduque julianduque merged commit 26ae5fd into main Oct 7, 2025
1 of 2 checks passed
@julianduque julianduque deleted the v5 branch October 7, 2025 02:22
Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR is being reviewed by Cursor Bugbot

Details

You are on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle.

To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

@@ -26,7 +26,7 @@ describe("HerokuEmbeddingModel", () => {
describe("Constructor", () => {
it("should initialize with correct properties", () => {
expect(model.modelId).toBe(testModel);
expect(model.specificationVersion).toBe("v1");
expect(model.specificationVersion).toBe("v2");
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: Heroku Embedding Model Version Uncertainty

The HerokuEmbeddingModel constructor test was updated to expect specificationVersion 'v2'. It's unclear if 'v1' or 'v2' is the correct version for this model after the AI SDK v5 migration.

Fix in Cursor Fix in Web

}
const supportedChatModels = [
"claude-3-5-sonnet-latest",
"claude-4-sonnet",
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: Duplicate Model Entry in Supported List

The supportedChatModels array includes 'claude-4-sonnet' twice, creating a redundant entry in the list of supported models.

Fix in Cursor Fix in Web

if (options.providerOptions &&
Object.keys(options.providerOptions).length > 0) {
console.warn("providerOptions are not supported for Heroku embedding models. Ignoring provided options.");
}
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: Signal Handling Delay in Embed Function

The doEmbed function's abort signal check is not the very first executable statement, allowing minimal processing before an aborted request is detected.

Fix in Cursor Fix in Web

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants