Repository navigation
data(oss): openapi-sampler #223 is merged - #4
Conversation
Redocly merged the XML fixes on 28 Oct 2026 after makare11a's approval, so the Redoc entry no longer says they await review. Evidence now pins #223 as merged into main plus the approval comment, and the ledger records the new state and updatedAt, so the weekly re-check stays green. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01117LuacuBxMJUn1wJkfdyL
The previous commit copied #882's reason onto #883 by mistake; this puts back "Resolved by a change to my own config." so the only ledger change in this PR is openapi-sampler #223. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01117LuacuBxMJUn1wJkfdyL
|
No actionable comments were generated in the recent review.
 |
| Layer / File(s) | Summary |
|---|---|
Update merge evidence and status display data/open-source.json, data/open-source-ledger.json, README.md |
The evidence records PR 223 as merged on main and adds supporting comments. The ledger state and timestamp are updated. The Redoc text now reports the merge. |
Estimated code review effort: 1 (Trivial) | ~3 minutes
Change: Other
Possibly related PRs
- rishitank/rishitank#2: It records the same
openapi-sampler#223entry as awaiting review. This change updates that entry to merged. - rishitank/rishitank#3: It establishes the data records and README generation flow that this change updates.
Merge Risk: 
c5fe3
-
The status and supporting evidence updates are ready to merge with no identified blocking risk.
Pre-merge checks: 
-
Check name Status Explanation Title check The title clearly identifies the main change: recording that openapi-sampler issue #223was merged.Description check The description is directly related to the changeset and explains the data updates, evidence, generated README change, and validation checks. Docstring Coverage No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat… Linked Issues check Check skipped because no linked issues were found for this pull request. Out of Scope Changes check Check skipped because no linked issues were found for this pull request. Full details: Docstring Coverage
-
Explanation
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (2 skipped: 2 unsupported.)
-
- 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.
Apprentice, the status now shines merged.
Evidence records the path to main.
The ledger marks the time and state.
Redoc speaks with one clear voice.
The rebel scum of stale claims retreat.
The Dark Side keeps the record straight.
Independent review (Claude, separate session context)No blocking findings. Every claim in the changed entry was checked against GitHub:
Findings
Merge after CodeRabbit finishes. |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Two developers on Redocly/redoc#2347 report the same issue (LeWolOnline: "I'm experiencing the same issue it solves"; ndmitrys: "Oh, I'm experiencing the same issue"), and a third asks for an update. The 15 Oct wording "another developer" undercounted; ndmitrys's comment is added as evidence. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01117LuacuBxMJUn1wJkfdyL
|
One more fix, in
So the text now says "other developers", and ndmitrys's comment is added as evidence. The 15 Oct review that changed it to "one other developer" was wrong. Local checks: |
|
@coderabbitai review |
Action performed
|
What
The Redoc entry said my XML fixes to openapi-sampler "await review". Redocly/openapi-sampler#223 was approved by makare11a on 26 Oct 2026 and squash-merged into
mainon 28 Oct (dc4e5c0).data/open-source.json: the text now says they "were merged after review". The #223 evidence pinsmerged: true, base: main(wasstate: open) and adds makare11a's approval comment.data/open-source-ledger.json:Redocly/openapi-sampler#223→state: merged,updatedAt: 2026-10-28T15:11:58Z(GitHub's current value).README.md: regenerated byscripts/oss/render-readme.mjs.Why now
The weekly job would normally propose this. Its 26 Oct run failed at the curate step: the token was present, but the Claude run returned an error after about 0.5 s, cause not yet diagnosed. And from the next run its claim check would fail, because #223 is no longer open.
Not claimed
No release is named: openapi-sampler's latest release is still v1.7.9 (21 Oct), and the release PR (#231) is open. "Merged after review" rests only on the merged PR and the approval comment.
Checks
node --test tests/*.test.mjs: 44 passnode scripts/oss/validate.mjs: OK, 14 entries, ledger 70 items (21 included)render-readme --check: in stepverify-claims: run by this PR'sci-gateagainst the live API (it can't reach the API from my session).The branch has two commits: the second restores one ledger reason (
webpack/css-loader#883) that the first copied wrongly. Squash on merge; the net diff is 3 files, +6/−5.🤖 Generated with Claude Code
https://claude.ai/code/session_01117LuacuBxMJUn1wJkfdyL