Skip to content

[SECURITY] Update Chromium to 158.0.8127.37 - #26

Merged
ignaciojuarez merged 5 commits into
mainfrom
update/chromium-158
Nov 18, 2026
Merged

ignaciojuarez merged 5 commits into
mainfrom
update/chromium-158

Conversation

@ignaciojuarez

Copy link
Copy Markdown
Owner

Moves the SDK from Chromium 157.0.8103.39 to the current Mac Stable, 158.0.8127.37 (b8c2be8), with depot_tools 7a33907.

Changes

  • All 42 patches rebased. Three conflicts were resolved by hand: the reading-mode controller setup, the sad-tab BrowserView check (now an early return in place of upstream's CHECK), and the loading-predictor includes.
  • 0001: Chromium 158 builds the app executable from a minimal C launcher that links the framework directly. The old loader in chrome_exe_main_mac.cc now only reaches helpers, so the runtime started as stock Chromium. The Cobble client is now loaded at the start of ChromeMain for the browser process, using the framework's own already-loaded handle.
  • 0021: renderer process IDs are now typed ChildProcessId.
  • A test now uses the renamed WindowOpenDisposition::kNewPictureInPicture.
  • Docs: README, AGENTS and AUDIT now describe 158 only, plus a single-build-tree rule. On each update, build and validate in chromium-next, then delete the previous tree and unused runtimes.

Validation (local, Apple silicon)

  • Native harness: 256/256 native checks passed, plus navigation, DOM, forms, rendering, WebGL2, downloads, clean shutdown and empty History tables.
  • Python 74/74, node Tests/test_smoke_fixture.mjs, swift test (34), swift build --product CobbleChromiumClient.
  • Packaged runtime: cobble-sdk-158.0.8127.37-arm64-51e87dd144fd-e9ee3df7bc99.zip, sha256 d52df46e…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

ignaciojuarez and others added 5 commits November 17, 2026 21:11
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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant