chore: release v0.7.101 - #3106
Merged
Merged
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
vanceingalls
temporarily deployed
to
npm-publish
August 8, 2026 03:12 — with
GitHub Actions
Inactive
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
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.
What
Stable release v0.7.101, covering the 5 commits since v0.7.100.
This is the release that starts the parallel drawElement router rollout. #2840 merged after v0.7.100 was cut, so the ramp has not reached anyone yet — publishing this is what activates it.
Behavioural change worth reading before merging
On publish, 5% of installs begin using the parallel capture path by default on eligible renders (drawElement-capable, ≥700 frames, auto multi-worker). Everyone else is unaffected.
Safety properties that ship with it:
percentage: 0incanaryRegistry.tsis a full fleet-wide revert with no release needed.HF_DE_PARALLEL_ROUTER=falseopts a user out,=trueopts in early. Explicit choice wins in both directions.Ramp discipline after this ships
Hold at 5% until PRINFRA-372 resolves.
--workers autocrashes every worker ("detached Frame" / "Target closed") on macOS arm64 while--workers 1is clean, and the router forces 3 workers. PRINFRA-339 (indefinite stalls) and PRINFRA-354 (silent hang) are also open. None of those emitrender_complete, so neither the self-verify nor the breaker catches them — a repro harness is attached to PRINFRA-372 and needs a ≤16 GB darwin/arm64 host.At each step split revert rate by
cpu_countandis_docker— the two segments with near-zero coverage in today's trial population. Baseline: routed renders fail at 2–3.4%, stable across versions.Also in this release
HF_DE_PARALLEL_ROUTERstays breaker-managed rather than exempting the install from its own breakerNote on numbering
0.7.99 and 0.7.100 published normally and do not contain the router work.
🤖 Generated with Claude Code