# Flags SDK 4.2.2

- Product: Flags SDK (https://whatsnew.fyi/product/flags-sdk)
- Vendor: Vercel
- Date: 2026-07-24
- Version: 4.2.2
- Original notes: https://github.com/vercel/flags/releases/tag/flags%404.2.2
- Permalink: https://whatsnew.fyi/product/flags-sdk/releases/4.2.2

What's New is an index, not a publisher: every entry below links to the vendor's own release notes, which are the authoritative source. Entries are labelled where they are hand-curated sample data, pre-releases, or drawn from a secondary source such as a developer blog.

Reuse: the summaries, labels and curation here are © What's New. Quote freely with attribution and a link back; wholesale republication of the corpus is not permitted — terms: https://whatsnew.fyi/terms. The vendors' own release notes remain their publishers'.

---

- **fixed** — Tracing no longer records Next.js control-flow errors as span errors, instead reporting flag evaluation spans as successful when redirects, notFound, or rejected hanging promises of aborted prerenders are re-thrown for the framework to handle

###### Patch Changes

-   [#438](https://github.com/vercel/flags/pull/438) [`d23d9d2`](https://github.com/vercel/flags/commit/d23d9d2b7ab04bb72c8682c0811f20dd6699104f) Thanks [@eps1lon](https://github.com/eps1lon)! - Tracing no longer records Next.js control-flow errors as span errors. Redirects, notFound, and the rejected hanging promises of aborted prerenders (`HANGING_PROMISE_REJECTION`) are re-thrown for the framework to handle, but the flag evaluation span previously reported them via `span.setStatus({ code: 2, message })`, polluting traces with errors like "During prerendering, `connection()` rejects when the prerender is complete" on every aborted runtime prefetch. These spans are now reported as successful (status Ok), since the traced function completed as intended and the error is framework control flow, while genuine evaluation failures keep marking spans as errored.