Skip to content

docs(release): match v2.3.3 notes to established format - #621

Merged
ndycode merged 1 commit into
mainfrom
docs/release-v2.3.3-notes-tone
Jun 19, 2026
Merged

ndycode merged 1 commit into
mainfrom
docs/release-v2.3.3-notes-tone

Conversation

@ndycode

@ndycode ndycode commented Jun 19, 2026 •

Copy link
Copy Markdown
Owner

Rewrites docs/releases/v2.3.3.md to the same voice and structure as recent releases (v2.3.1 / v2.3.2):

  • Subsystem ## sections (Runtime Rotation / Recovery, Quota / Forecast, Request / SSE Data Path, Storage / Auth / Logging, Testing, Notes).
  • ### Bugfixes / ### Behavior / ### Improvements subsections.
  • Dense scenario → mechanism → fix prose bullets carrying the PR reference, instead of the prior terse changelog-style list.

Wording only — no change to which fixes are described. test/documentation.test.ts passes (26/26).

🤖 Generated with Claude Code

note: greptile review for oc-chatgpt-multi-auth. cite files like lib/foo.ts:123. confirm regression tests + windows concurrency/token redaction coverage.

Greptile Summary

pure documentation rewrite of docs/releases/v2.3.3.md to match the voice and structure established by v2.3.1/v2.3.2 — no functional code changes, no new fixes added or removed.

  • replaces terse changelog-style bullets with dense scenario → mechanism → fix prose, substitutes internal tracking codes (H1–H7, M1, M3, I1, I2, L3) with github pr references (fix: harden rotation, persistence, and SSE failure handling (stress audit) #617–fix: close remaining stress-audit findings (I1, I2, M3, L3, H1-at-source) #619), and adds ## subsystem sections with ### Bugfixes / ### Behavior / ### Improvements nesting.
  • correctly promotes the response.incomplete early-stop note out of ### Bugfixes into its own ### Behavior subsection, which is a small accuracy improvement over the prior version.
  • the three multi-process concurrency fixes (unbounded rate-limit window, refresh-lease ownership nonce, cross-process token clobber) and the windows-fsync durability fix in the local-client-token store remain accurately described; token-safety and filesystem-safety prose is preserved and expanded.

Confidence Score: 5/5

documentation-only rewrite with no runtime code touched; safe to merge.

every bug description from the prior version is faithfully preserved in the rewrite, the response.incomplete note is more accurately placed in ### Behavior rather than ### Bugfixes, and the windows-fsync / token-safety language around the local-client-token store and cross-process refresh clobber is expanded rather than weakened. no logic, config, or test code was changed.

no files require special attention.

Important Files Changed

Filename Overview
docs/releases/v2.3.3.md documentation-only rewrite matching the v2.3.1/v2.3.2 format; all bug descriptions preserved, response.incomplete correctly reclassified to ### Behavior, internal tracking codes replaced with PR refs (#617–#619).

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["docs/releases/v2.3.3.md"] --> B["## Runtime Rotation / Recovery"]
    A --> C["## Quota / Forecast"]
    A --> D["## Request / SSE Data Path"]
    A --> E["## Storage / Auth / Logging"]
    A --> F["## Testing"]
    A --> G["## Notes"]

    B --> B1["### Bugfixes\n- unbounded rate-limit window (#617)\n- refresh lease nonce (#617)\n- cross-process token clobber (#617)"]
    C --> C1["### Bugfixes\n- transient 429 deferral (#617)\n- live-quota forecast inversion (#617)"]
    D --> D1["### Bugfixes\n- SSE error → non-2xx (#617, #618)\n- data: parser trailing space (#617)"]
    D --> D2["### Behavior\n- response.incomplete → 200 (#618)"]
    E --> E1["### Bugfixes\n- V1→V3 migration bodies (#619)\n- fsync before rename (#619)\n- expires_in validation (#619)\n- cma_local log masking (#619)"]
    F --> F1["### Improvements\n- regression coverage added\n- 4 tests updated"]
Loading
%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
    A["docs/releases/v2.3.3.md"] --> B["## Runtime Rotation / Recovery"]
    A --> C["## Quota / Forecast"]
    A --> D["## Request / SSE Data Path"]
    A --> E["## Storage / Auth / Logging"]
    A --> F["## Testing"]
    A --> G["## Notes"]

    B --> B1["### Bugfixes\n- unbounded rate-limit window (#617)\n- refresh lease nonce (#617)\n- cross-process token clobber (#617)"]
    C --> C1["### Bugfixes\n- transient 429 deferral (#617)\n- live-quota forecast inversion (#617)"]
    D --> D1["### Bugfixes\n- SSE error → non-2xx (#617, #618)\n- data: parser trailing space (#617)"]
    D --> D2["### Behavior\n- response.incomplete → 200 (#618)"]
    E --> E1["### Bugfixes\n- V1→V3 migration bodies (#619)\n- fsync before rename (#619)\n- expires_in validation (#619)\n- cma_local log masking (#619)"]
    F --> F1["### Improvements\n- regression coverage added\n- 4 tests updated"]
Loading

Reviews (1): Last reviewed commit: "docs(release): match v2.3.3 notes to est..." | Re-trigger Greptile

Rewrite the v2.3.3 release notes to the same voice and structure as recent
releases (v2.3.1/v2.3.2): subsystem sections with Bugfixes/Behavior/Improvements
subsections and dense scenario->mechanism->fix prose bullets carrying the PR ref,
instead of the prior terse changelog-style list. No content change beyond wording.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@chatgpt-codex-connector

Copy link
Copy Markdown

Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits.
Credits must be used to enable repository wide code reviews.

@coderabbitai

coderabbitai Bot commented Jun 19, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@ndycode, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 2 minutes and 3 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

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 credits.

🚦 How do rate limits work?

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

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, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 901bcfbe-1c3e-4727-ab45-02a68027a4fb

📥 Commits

Reviewing files that changed from the base of the PR and between 826dc07 and 7155560.

📒 Files selected for processing (1)
  • docs/releases/v2.3.3.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/release-v2.3.3-notes-tone
✨ Simplify code
  • Create PR with simplified code
  • Commit simplified code in branch docs/release-v2.3.3-notes-tone

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 and usage tips.

@ndycode
ndycode merged commit 8360f85 into main Jun 19, 2026
1 of 2 checks passed
@ndycode
ndycode deleted the docs/release-v2.3.3-notes-tone branch June 19, 2026 10:07
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