Chrome Releases (Security Updates)

https://chromereleases.googleblog.com/

Chrome / ChromeOS Stable & Beta channel releases, primary citation for Chrome 0-day fixes (added 2026-05-08). Filter for 'Stable Channel Update' posts that reference CVEs / 'in the wild'. RSS at https://feeds.feedburner.com/GoogleChromeReleases also works. | 2026-06-20 full audit (v2.62): live=Y, drill=Y. FETCH → feed https://feeds.feedburner.com/GoogleChromeReleases 5 (filter for 'Stable Channel Update' posts referencing CVEs / 'in the wild'); feed summary carries the body, or webfetch the per-post chromereleases.googleblog.com URL. AVOID: Don't burn calls fetching every Beta/Dev/iOS channel post; only Stable Channel desktop updates carry the CVE/0-day security content.. | 2026-07-05 admiralty audit: A (vendor-psirt), Google's own Chrome release channel, primary source for Chrome fixes; feed clean. Status stays active. Filter for Stable Channel desktop posts. | 2026-08-10: DEFECT: the feed subcommand returned 0 items for S1 this run despite the source being live; listing-extraction/recipe drift, not a transport block. Needs a recipe pass, do not demote (content axis unaffected). | 2026-08-11: feed-extraction defect CONFIRMED for a second consecutive run, `fetch_source.py feed https://chromereleases.googleblog.com/feeds/posts/default` routes via jina and returns count=0, and a direct GET of the listing returns the Blogger shell with no posts in the body. Next recipe attempt should try the explicit RSS alias `.../feeds/posts/default?alt=rss` or a dated archive path such as /2026/08/. | 2026-08-13: feed https://chromereleases.googleblog.com/feeds/posts/default returned count=0 for the third consecutive run; the dated listing page https://chromereleases.googleblog.com/2026/ is fetchable directly and is the working fallback. 403/empty-feed never demotes. | 2026-08-15: feeds/posts/default still returns count=0 (fourth consecutive run); the dated archive page chromereleases.googleblog.com/<year>/ is the working recipe and was used this run. | 2026-09-29: rss_url pinned to https://chromereleases.googleblog.com/feeds/posts/default (fetch_method is rss but the feed lived only in the notes, so it never reached the research slice). (2026-09-29 operator-directed setup review) | 2026-10-02 (2026-10-02T0404Z-intel): recipe is `python3 tools/fetch_source.py extract https://chromereleases.googleblog.com/` (front page lists the newest posts with links), then `extract <post URL>` for the build and the Security changes section; the Atom feed answers HTTP 302 on the direct transport. Health recipe: the front page lists only post titles, the Stable-updates label page carries the Security Fixes sections (health_cmd). | 2026-10-06 (S1, not re-verified by the main agent): `extract https://chromereleases.googleblog.com/search/label/Stable%20updates` returns the Security Fixes sections with build numbers; the front page lists only titles. | 2026-10-10: the feed answers HTTP 302 on direct fetch and `extract` of the label page returns only the newest post (ChromeOS); no working command found for desktop stable posts this run. | 2026-10-12: recipe fixed by S1: `python3 tools/fetch_source.py feed https://feeds.feedburner.com/GoogleChromeReleases 25` reads direct (25 dated items). The blogspot feed 302-redirects to the http:// feedburner URL, which the tool refuses to follow; the per-post links in the feed are http:// and fail every transport, so rewrite them to https:// and `extract` reads them. | 2026-10-14 intel run: working recipe: the feedburner feed with the post links rewritten from http:// to https://, then extract each post. | 2026-10-15 (S1): the failing 302 was the http:// post link, not the feed. `feed https://feeds.feedburner.com/GoogleChromeReleases 20` reads direct; rewrite the post link to https:// and run `extract` on it. | 2026-10-17 (2026-10-17T0256Z-intel): S1: `feed https://feeds.feedburner.com/GoogleChromeReleases 20` reads direct; the item links are http:// and answer 302, so rewrite them to https:// and read each post with `extract https://chromereleases.googleblog.com/2026/10/<slug>.html`. | 2026-10-11 quality audit: working stable-channel recipe: feed https://chromereleases.googleblog.com/feeds/posts/default/-/Stable%20updates?alt=rss&max-results=20 30, then extract per post. | 2026-10-25 (2026-10-25T1308Z-audit): G1 re-sweep: feed item links are http; rewrite them to https before `extract`.