docs: Chromium ships a major every two weeks, not four#30

merged1
main
docs/two-week-cadence
opened1d agobyKKainoa Newton
View on GitHubTwo-way sync enabledPR last imported 12h ago

Problem. docs/internals/overview.md says Chromium ships a major "roughly every four weeks". Since M153 (2026-09-08) stable majors come every two weeks: M154 09-22, M155 10-06, M156 10-20 (Chrome blog). This is one of the claims listed in the rac-baseline digest for gate G7.

Change. One line.

Verified. Docs only, so there's nothing to build. No other "four weeks" in the repo outside helium-chromium/, which I searched.

🤖 Generated with Claude Code (Claude Opus 5.5)


Note

Low Risk Documentation-only wording fix with no runtime, build, or security impact.

Overview Updates docs/internals/overview.md so the “Patch design for low-maintenance updates” section reflects current Chromium stable cadence: every two weeks since M153, instead of “roughly every four weeks.”

The rest of the guidance (refreshing rac patches each release, favoring new files and small hooks) is unchanged—only the release-frequency claim is corrected for reviewers and maintainers planning patch refresh work.

Reviewed by Cursor Bugbot for commit 8b9cc2ade7f136af8f9b15e31d3b546552e9a058. Bugbot is set up for automated code reviews on this repo. Configure here.


Summary by cubic

Fixes the Chromium release cadence in docs/internals/overview.md from roughly every four weeks to every two weeks, matching the current schedule since M153.

Written for commit 8b9cc2ade7f136af8f9b15e31d3b546552e9a058. Summary will update on new commits.

View guided diff Turn on auto-fix

Checks

2 failing · 9 successful · 2 neutral · 1 skipped
Some checks failed

Failing2

  • pullfrogGitHub
    Failed
  • VercelGitHub
    Failed
8b9cc2a

Added 1 commit

  • docs: Chromium ships a major every two weeks, not four8b9cc2a
Synced from GitHub

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

External image Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: 1832474a-5548-498a-b3c6-4d33fb9a64ee

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

CcursorBot1d ago
Synced from GitHub

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: ef0ea7e8-785a-4008-b987-79f68c8b2655)