Bun

Bun’s blog is the primary release-notes surface: each major version gets a post mixing feature announcements with incompatibility disclosures and resolved compatibility gaps. The two concerns share the same page, so readers hunting for breakage have to read past the performance benchmarks to reach the changelog substance.

The more precise surface for day-to-day debugging is the Node.js compatibility table at bun.sh/docs/runtime/nodejs-compatibility, which tracks which APIs are fully implemented, partially implemented, or absent. That table updates independently of the release cycle, and it is where the gap between “works in Node” and “silently misfires under Bun” is most likely to be named.