Repository navigation
[SECURITY] Update Chromium to 158.0.8127.37 - #26
Merged
Merged
Conversation
Rebase all 42 patches from 157.0.8103.39 to 158.0.8127.37 (Mac Stable) with depot_tools from the same week. Three conflicts were resolved by hand where upstream rewrote nearby code (reading-mode controller setup, the sad-tab BrowserView check, loading predictor includes). Chromium 158 passes renderer process IDs as ChildProcessId, so the client-certificate context hook now takes that type, and the PiP test reads the renamed WindowOpenDisposition::kNewPictureInPicture. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Document the update rule: build and validate the new version in chromium-next, then delete the previous tree, rename to the version-neutral chromium path and drop unused runtimes. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Chromium 158 builds the app executable from a minimal C launcher that links the framework directly, so the old loader in chrome_exe_main_mac.cc only reached helpers and the runtime started as stock Chromium. Load CobbleChromiumClient.dylib at the start of ChromeMain for the browser process instead, passing the framework's own already-loaded handle. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Nov 18, 2026
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.
Moves the SDK from Chromium 157.0.8103.39 to the current Mac Stable, 158.0.8127.37 (
b8c2be8), with depot_tools7a33907.Changes
CHECK), and the loading-predictor includes.chrome_exe_main_mac.ccnow only reaches helpers, so the runtime started as stock Chromium. The Cobble client is now loaded at the start ofChromeMainfor the browser process, using the framework's own already-loaded handle.ChildProcessId.WindowOpenDisposition::kNewPictureInPicture.chromium-next, then delete the previous tree and unused runtimes.Validation (local, Apple silicon)
node Tests/test_smoke_fixture.mjs,swift test(34),swift build --product CobbleChromiumClient.cobble-sdk-158.0.8127.37-arm64-51e87dd144fd-e9ee3df7bc99.zip, sha256d52df46e…dddfa,release_ready: false.Real sites, hardware and release qualification remain open.
Supersedes the lock-only proposals #18, #20, #23 and #24.
🤖 Generated with Claude Code