Skip to content

docs: source-mirror retention + offer-durability policy - #501

Merged
bryan-minimal merged 1 commit into
mainfrom
docs/source-mirror-retention
Jul 21, 2026
Merged

docs: source-mirror retention + offer-durability policy#501
bryan-minimal merged 1 commit into
mainfrom
docs/source-mirror-retention

Conversation

@bryan-minimal

Copy link
Copy Markdown
Member

Adds the durability paragraph to LICENSING.md §3: the source mirror's objects are write-once and the bucket now carries a three-year retention policy (the GPLv2 §3(b) written-offer period — applied 2026-07-21, unlocked). Notes the periodic-review caveat (retention runs from upload; the offer lasts while the binary is distributed), the weekly presence sweep, and that obligations follow the public endpoint if distribution moves.

Docs only.

🤖 Generated with Claude Code

States the mirror's durability posture: write-once objects, three-year
bucket retention (the GPLv2 written-offer period), periodic review since
the offer lasts while the binary is distributed, the weekly presence
sweep, and that obligations follow the public endpoint if distribution
moves.
@coderabbitai

coderabbitai Bot commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 56 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 46cb9f68-309f-486a-8d7d-6671ca13797a

📥 Commits

Reviewing files that changed from the base of the PR and between ae08be2 and 05a4096.

📒 Files selected for processing (1)
  • LICENSING.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/source-mirror-retention

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

@bryan-minimal
bryan-minimal added this pull request to the merge queue Jul 21, 2026
Merged via the queue into main with commit 0fc7299 Jul 21, 2026
10 checks passed
@bryan-minimal
bryan-minimal deleted the docs/source-mirror-retention branch July 21, 2026 19:52
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.

2 participants