Chrome Release → Fixing CL Mapper Maps every security fix in a Chrome Releases blog post to the Gerrit CL(s) that fixed it. Input — a URL. If empty, ask the user for one. Procedure 1. Extract CVE → bug ID pairs from the blog post The blog HTML buries bug IDs inside tags, so strip tags first. Run: If this yields nothing, the page may have changed format — fall back to and and pair them by order. 2. Find the fixing CL for each bug Search git history in the Chromium checkout and relevant sub-repos for commits whose or footer references the bug ID, then extract the Gerrit URL. Repo selection by c…