Skip to content

feat: V4 migration guide - #2627

Open
Luca Forstner (lforst) wants to merge 2 commits into
mainfrom
lforst/dum-e/berlin-b5bea5b5b9
Open

Luca Forstner (lforst) wants to merge 2 commits into
mainfrom
lforst/dum-e/berlin-b5bea5b5b9

Conversation

@lforst

Copy link
Copy Markdown
Member

No description provided.

**Node.js:** The supported version range is now `^20.12.0 || >=22.13.0`.
This drops support for Node 18, Node 21, and Node 22 versions before 22.13.0.

**Provider libraries:** Support for the following versions has been removed:

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

while we are here, should we increase min versions for anything else?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

I did some analysis and there are some candidates but nothing that would meaningfully let us clean up things.

Top candidates to drop were Transformers.js 3.0–3.3 which is 2.85% of it's download share. And Claude Agent SDK 0.1.x which is 3.09%.

Comment thread docs/migration-v3-to-v4.md Outdated
- Eve versions before v0.34.0; upgrade to v0.34.0 or newer.
- Flue versions before v1; upgrade to v1 or newer.

Upgrade Braintrust integration packages alongside `braintrust`, using releases compatible with v4.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

we should be explicit about this, or just remove the note all together

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

true

```ts
initLogger({
projectName: "my-project",
captureAttachments: true,

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

should we call this autoCaptureAttachments? idk this is fine too, this is just bikeshed.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

yes gonna update that

### Temporal

`@braintrust/temporal` now propagates `traceparent`, `tracestate`, and `baggage` instead of the `_braintrust-span` and `_braintrust-workflow-span*` headers.
Upgrade clients and workers together.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

what does this mean?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Temporal has clients and servers. And if you update braintrust on the client but not on the server (or vice versa) you may have broken traces.

This branch has not been deployed

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants