docs: x64 ships one Nehalem binary; drop Haswell/baseline distinction - #36465
Open
robobun wants to merge 3 commits into
Open
docs: x64 ships one Nehalem binary; drop Haswell/baseline distinction#36465robobun wants to merge 3 commits into
robobun wants to merge 3 commits into
Claude / Claude Code Review
completed
Jul 30, 2026 in 11m 19s
Code review found 1 potential issue
Found 1 candidates, confirmed 1. See review comments for details.
Details
| Severity | Count |
|---|---|
| 🔴 Important | 0 |
| 🟡 Nit | 1 |
| 🟣 Pre-existing | 0 |
| Severity | File:Line | Issue |
|---|---|---|
| 🟡 Nit | test/internal/release-asset-coherence.test.ts:83-93 |
npm package READMEs still describe -baseline as "without AVX2 instructions" |
Annotations
Check warning on line 93 in test/internal/release-asset-coherence.test.ts
claude / Claude Code Review
npm package READMEs still describe -baseline as "without AVX2 instructions"
The npm package READMEs still carry the same stale "without AVX2" / "do not support AVX2" claims this PR removes from `docs/`: `packages/bun-release/npm/bun/README.md` (L21/24/26) and each `packages/bun-release/npm/@oven/bun-{darwin,linux,windows}-x64-baseline/README.md` (L5). Since the new `installation.mdx` `<Note>` explicitly names the `@oven/bun-*-x64-baseline` packages as aliases, these are same-class sibling sites — worth updating here so npmjs.com doesn't keep telling users baseline is a
Loading