Repository navigation
docs: prepare worker termination and allocator exit release - #20
Merged
Merged
Conversation
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.
Prepare the next immutable ten-archive release with the already merged worker heap-cap termination fix (#18) and mimalloc process-exit TLS fix (#16).
The release notes now lead with those fixes, explain that standard Bun builds disable the affected allocator teardown, retain the previous engine changes, and credit @dylan-conway for the allocator diagnosis. The existing changelog entries move into a dated release section with an empty Unreleased section. Engine source and publication workflows are unchanged.
Validation: the entire change is documentation-only relative to release head f88d5f3; scoped P2 Codex review is clean. Publication will rebuild all ten archives and pass the existing protected qualification and independent public-readback gates. The GC-cadence change in #14 remains separate while its performance gate is unresolved.
Final exact-head validation: engine checks and Linux ARM64 regressions both passed at f27d27f, including native Windows ARM64 execution.