release: FixMap v0.8.7 - #448
Merged
Merged
Conversation
Publishes the vendored-bundle detection fix. It was merged to main before this release, and for a short window the website changelog described it as shipped while npm still served 0.8.6 without it — the #274 defect with its polarity reversed, advertising a fix the released artifact lacked rather than an accuracy figure it no longer achieved. The website changelog loses its "Unreleased / In progress" section, and the render branches that produced "Coming next" are removed rather than left unused. An entry describing work that has only landed on main tells a reader a fix is available when npm install will not give it to them; the type now documents that every entry must be an installable version. Versions move to 0.8.7 across root, core, cli, action, server.json and the lockfile, with the README Action pin. apps/web keeps 0.0.0 — it is unpublished and publish.yml validates only its core dependency. The lockfile was patched by hand; regenerating on Windows drops the @emnapi entries Linux CI needs (9 present, verified). Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Publishes the vendored-bundle detection fix from #446, and removes the website's unreleased state.
Why this release exists
The #446 fix was merged to
main, but npm still served 0.8.6 without it — and/changelogtold visitors it was fixed. Verified against the same fixture:@aryam/fixmap@0.8.6compiled/react-dom/cjs/react-dom.development.js#1, high, score 16mainThe Action was affected too: the fix commit lands after the
v0.8.6tag, so anyone pinning@v0.8.6did not get it either.This is #274 with its polarity reversed — the site advertising a fix the released artifact lacks, rather than an accuracy figure it no longer achieves.
The structural fix, not just the release
/changeloghad anUnreleased / In progressentry, plus render branches producing "Coming next" and "Next". Both are removed, and theReleasetype now documents that every entry must be an installable version. Leaving the branches in place would have made this recoverable by accident; removing them means reintroducing an unreleased section has to be deliberate.Verification
npm run cigreen. Server manifest and Action metadata checks pass. Release-notes extraction fromCHANGELOG.mdconfirmed for the 0.8.7 heading —publish.ymlfails the release if that section is missing.Held-out 7/12 · 8/12 · 9/12 and external 11/16 · 16/16 · 16/16 unchanged; adversarial 9/9 with the new pretty-printed vendored-bundle fixture.
apps/webkeeps0.0.0deliberately — unpublished, andpublish.ymlvalidates only its core dependency. The lockfile was patched by hand (9@emnapientries verified present).🤖 Generated with Claude Code