Skip to content

docs(matrix): bring release markers up to cachekit-py 0.23.0 and cachekit-rs 0.11.0 (LAB-10702) - #208

Merged
27b-merge-warden[bot] merged 2 commits into
mainfrom
lab-10702-matrix-release-markers
Oct 24, 2026
Merged

27b-merge-warden[bot] merged 2 commits into
mainfrom
lab-10702-matrix-release-markers

Conversation

@27Bslash6

Copy link
Copy Markdown
Contributor

What

Release markers only. Sixteen markers in sdk-feature-matrix.md called a PR unreleased that a published release carries; each now names the first release that carries it. Three phrases called an SDK's python-frame.json copy "the current revision" when it vendors an older one; each now names that revision. No cell's status or claim changes otherwise.

Line Marker First release
117 cachekit-io/cachekit-py#514 (File backend expired_entry read) 0.23.0
298 cachekit-io/cachekit-py#550 (temporal sentinel vectors in CI) 0.23.0
301 cachekit-io/cachekit-py#520 (X-TTL, fractional TTLs) 0.23.0
302 cachekit-io/cachekit-py#397 (empty key), so "Compliant on main, unreleased" becomes "Compliant" 0.21.0
199 (fn 10) cachekit-io/cachekit-rs#147 (SWR refresh never waits on another fill) 0.11.0
301 cachekit-io/cachekit-rs#142 (sub-second refresh_ttl) 0.11.0
303 cachekit-io/cachekit-rs#152 ×2, #146, #158, #158 + #160, #150 + #160 0.11.0
309 (fn 15) cachekit-io/cachekit-rs#140 (auto mode rejects trailing bytes); "on main" reworded too 0.11.0
311 (fn 16) cachekit-io/cachekit-rs#158, #158 + #160, #160 0.11.0

Footnote 16 also has four "(py since 0.23.0, ts since npm 0.2.1)" notes on fixtures that cachekit-rs vendors in cachekit-io/cachekit-rs#146 and #152. Leaving rs out read as unreleased, so each gains "rs since 0.11.0".

python-frame.json: the TypeScript "Test vectors in CI" cell (cachekit-io/cachekit-ts#230) and footnote 16 (cachekit-io/cachekit-rs#160, cachekit-io/cachekit-ts#230) now name the cachekit-io/protocol#180 revision.

Left as they are, still correct: the markers naming cachekit-io/cachekit-py#618 and #627, because PyPI's latest is 0.24.1 and the 0.25.0 release PR (cachekit-io/cachekit-py#619) is still open. Also the TypeScript markers naming cachekit-io/cachekit-ts#240 and #245, which wait on an npm release whose bindings embed cachekit-core 0.7.0, and the historical "🚧 Unreleased" sentence under the Reliability table. The Python Wire format (ByteStorage) cell is not touched.

Verification

…it-rs PR

Sixteen markers called a PR unreleased that a published release carries:
four cachekit-py PRs (0.21.0, 0.23.0) and twelve cachekit-rs markers (0.11.0),
checked with git tag --contains on each merge commit and against the PyPI wheels
and crates.io .crate files. Footnote 16's py/ts release notes gain the rs floor.

The TypeScript test-vectors cell and footnote 16 called the cachekit-rs and
cachekit-ts python-frame.json copies the current revision; both hash to the
protocol#180 revision, one behind main.
@coderabbitai

coderabbitai Bot commented Oct 23, 2026 •

Copy link
Copy Markdown
Contributor

Review in Change Stack →

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration
📥 Commits

Reviewing files that changed from the base of the PR and between 0a1c6e8 and cf4f63d.

📒 Files selected for processing: 2
  • changelog.d/20261024_lab-10702.md
  • sdk-feature-matrix.md

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

Summary by CodeRabbit

  • Documentation
    • Updated the SDK feature matrix to reflect features shipped in Python 0.23.0 and Rust 0.11.0.
    • Recorded release status for expired-entry handling, refresh behaviour under lock contention, TTL refresh fixes, empty-key validation, temporal-sentinel tests and protocol-vector coverage.
    • Noted that rejecting trailing bytes in Rust auto mode is available from 0.11.0.

Walkthrough

The changelog and feature matrix update Python and Rust release markers, compliance entries, and protocol-vector coverage. They also record Python and TypeScript markers that remain unchanged.

Changes

SDK release markers

Layer / File(s) Summary
Feature and compliance release status
sdk-feature-matrix.md, changelog.d/20261024_lab-10702.md
The matrix records Python and Rust feature, compliance, and protocol-vector updates as released. The changelog summarises the updates and notes markers that remain unchanged.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Other

Possibly related PRs

Merge Risk: ⚪ Minimal · up to cf4f6

The release-marker documentation changes are ready to merge.

Pre-merge checks: Passed 5
Check name Status Explanation
Title check Passed The title clearly summarises the main change: updating SDK feature-matrix release markers for cachekit-py 0.23.0 and cachekit-rs 0.11.0.
Description check Passed The description directly explains the release-marker and python-frame.json revision updates, including the affected releases, unchanged markers, and verification performed.
Docstring Coverage Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (2 skipped: 2 unsupported.)

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR
  • 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.

@kodus-27b

kodus-27b Bot commented Oct 23, 2026 •

Copy link
Copy Markdown

Code Review Completed! 🔥

The code review was successfully completed based on your current configurations.

Kody Guide: Usage and Configuration
Interacting with Kody
  • Request a Review: Ask Kody to review your PR manually by adding a comment with the `@kody start-review` command at the root of your PR.

  • Provide Feedback: Help Kody learn and improve by reacting to its comments with a 👍 for helpful suggestions or a 👎 if improvements are needed.

Providing Context (Files & MCPs)

Add these hints in your PR description (or a comment) to unlock deeper checks:

  • Ticket / Acceptance Criteria: `Refs: ABC-123` (Linear/Jira/Asana/ClickUp/Trello) or a direct ticket link.
  • Bugfix Validation: a Sentry/Datadog/Bugsnag event link (or paste the stack trace/error message).
  • Endpoint Risk: mention the route (e.g., `POST /api/payments`) or controller/action name.
  • Attach a repo file as context: use an explicit marker like `@file:docs/guide.mdx#L10-L50` (replace with your real path).
  • API Contract Docs: include `@file:openapi.yaml` or `@file:swagger.json` when changing routes/schemas.
  • Definition of Done / Standards: include `@file:DOD.md` or `@file:CONTRIBUTING.md` if your repo has them.
  • Design System Source of Truth: include `@file:ui/index.ts` (replace with your DS entrypoint path).
  • Feature Flags: include the flag key/name and `@file:flags.ts` / `@file:config.json` (and optionally the PostHog flag name).
  • Edge/CDN Rules: link the Cloudflare rule/zone or describe the intended redirect/header behavior.
  • Attach an MCP tool output: use `@mcp<provider|tool>` (replace with an installed MCP provider + tool, e.g., `@mcp<sentry|events.search>`).
Current Kody Configuration
Review Options

The following review options are enabled or disabled:

Options Enabled
Bug ✅
Performance ✅
Security ✅
Business Logic ✅

Access your configuration settings here.

kodus-27b[bot]
kodus-27b Bot previously approved these changes Oct 23, 2026
@kodus-27b

kodus-27b Bot commented Oct 23, 2026

Copy link
Copy Markdown

Code Review Completed! 🔥

The code review was successfully completed based on your current configurations.

Kody Guide: Usage and Configuration
Interacting with Kody
  • Request a Review: Ask Kody to review your PR manually by adding a comment with the `@kody start-review` command at the root of your PR.

  • Provide Feedback: Help Kody learn and improve by reacting to its comments with a 👍 for helpful suggestions or a 👎 if improvements are needed.

Providing Context (Files & MCPs)

Add these hints in your PR description (or a comment) to unlock deeper checks:

  • Ticket / Acceptance Criteria: `Refs: ABC-123` (Linear/Jira/Asana/ClickUp/Trello) or a direct ticket link.
  • Bugfix Validation: a Sentry/Datadog/Bugsnag event link (or paste the stack trace/error message).
  • Endpoint Risk: mention the route (e.g., `POST /api/payments`) or controller/action name.
  • Attach a repo file as context: use an explicit marker like `@file:docs/guide.mdx#L10-L50` (replace with your real path).
  • API Contract Docs: include `@file:openapi.yaml` or `@file:swagger.json` when changing routes/schemas.
  • Definition of Done / Standards: include `@file:DOD.md` or `@file:CONTRIBUTING.md` if your repo has them.
  • Design System Source of Truth: include `@file:ui/index.ts` (replace with your DS entrypoint path).
  • Feature Flags: include the flag key/name and `@file:flags.ts` / `@file:config.json` (and optionally the PostHog flag name).
  • Edge/CDN Rules: link the Cloudflare rule/zone or describe the intended redirect/header behavior.
  • Attach an MCP tool output: use `@mcp<provider|tool>` (replace with an installed MCP provider + tool, e.g., `@mcp<sentry|events.search>`).
Current Kody Configuration
Review Options

The following review options are enabled or disabled:

Options Enabled
Bug ✅
Performance ✅
Security ✅
Business Logic ✅

Access your configuration settings here.

@27Bslash6

Copy link
Copy Markdown
Contributor Author

@coderabbitai review

@coderabbitai

coderabbitai Bot commented Oct 24, 2026 •

Copy link
Copy Markdown
Contributor
✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@27b-merge-warden
27b-merge-warden Bot merged commit 69b7f80 into main Oct 24, 2026
5 checks passed
@27b-merge-warden
27b-merge-warden Bot deleted the lab-10702-matrix-release-markers branch October 24, 2026 01:01
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