Repository navigation
fix: bump WebKit for collector progress and worker cadence - #136
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.
What does this PR do?
Pin all ten archives from the immutable OpenClaw WebKit collector-progress and worker-cadence release. A passive collector now wakes and rechecks when its mutator begins waiting while shared helpers serve another heap. Budgeted workers can use young-generation collections while retaining full-GC heap-limit confirmation and bounded growth.
The consuming immediate-timer wakeup is already on main in #129.
WEBKIT_VERSIONderives from the manifest, so the complete manifest updates engine identity and every archive checksum together. The compatibility note and changelog describe the resulting behavior. Engine fixes: openclaw/WebKit#14 and openclaw/WebKit#21, with the wakeup companion on engine main in openclaw/WebKit#22.How did you verify your code works?
The protected engine publication passed all ten builds, native Windows ARM64 probes, both paired 46/46 selections, and the 85-row upstream-synced selection. The native GC regression observed passive collection, completed before helper release, and preserved roots without a stall or timeout. Independent unauthenticated readback verified all fourteen public files, source/tag binding, immutability, GitHub digests, licenses, and byte identity with the checked candidate.
On exact head
247fbb2f2bb71fb0c7898398c75156506c2cfe9b, native CI passed Linux 47/47 rows and macOS 52/52 rows, both with independent net checks. Its synthetic merge tree equals the reviewed head tree. Windows qualification passed both x64 and ARM64 builds, native smokes, 31/31 compatibility rows per architecture, and independent net checks. Archive/executable hashes and PE architectures were independently checked; these remain unsigned test artifacts.The same verified Linux CI executable passed 348 Worker/inspector cases with zero failures on an isolated host, plus the standalone immediate-GC timer regression from #129. Source and executable hashes remained unchanged. Configure-time tests pass 29/29, formatting and the complete fork selector pass, and the committed head is scoped-clean at P2.
The unchanged advisory Mordant job reports the existing resolver bare-boolean diagnostic across three targets; its workflow explicitly uses
continue-on-error: true. The unchanged auxiliary issue matcher cannot start because provider authentication is not configured. All required platform gates above pass. No Bun tag, Bun release, or OpenClaw runtime pin update is included.