[cachekit-release-bot]

🤖 I have created a release beep boop

0.26.0 (2026-11-01)

Features

• decorators: let async @cache opt out of the miss-path distributed lock (LAB-7166) (#667) (1e2295d)

Bug Fixes

• metrics: skip thread-state retirement once the interpreter is exiting (LAB-12087) (#679) (42d7aea)
• monitoring: make enable_prometheus_metrics=False stop recording (LAB-12038) (#681) (3d81a93)
• perf: name the cachekit, Python and CPU a terrain recording ran (LAB-11993) (#687) (251a2fa)
• perf: terrain canary records the L2 label without its padding (LAB-11993) (#676) (4b2c65c)

Performance Improvements

• decorators: a backed L1 hit skips the stats context and log kwargs (LAB-12115) (#686) (9c1bd7f)
• decorators: answer the L1-only hit in one lock-free call into the extension (LAB-12024) (#673) (8b17e51)
• ir: run the 2,600 Ir/op paths over 300,000 calls (LAB-12245) (#697) (0e15cb6)
• l1: skip the structure walk and object hook on a kept L1 entry (LAB-12023) (#671) (7fbdfbe)
• l1: sweep expired entries from a deadline heap in short lock holds (LAB-12117) (#683) (63cf745)
• memcached: pick the server natively, as pymemcache's rendezvous hash does (LAB-12116) (#680) (a79cc90)
• redis: an uncontended async miss waits on 3 round trips, not 5 (LAB-12118) (#682) (1ef1d05)
• serializers: decode StandardSerializer reads in Rust, bounds and decode in one pass (LAB-12030) (#674) (39b1bdf)
• write-behind: park an idle writer thread instead of starting one per miss (LAB-12005) (#692) (96141b7)

---

This PR was generated with Release Please. See documentation.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

• Source mode: Auto
• Repository: cachekit-io/cachekit-py
• Branch: main
• File: .coderabbit.yaml
• Commit: 1858882
• Layers: Repository YAML
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: d24cbf20-1f75-4c16-9226-02e191f3bfe8

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

• X
• Mastodon
• Reddit
• LinkedIn

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

📢 Thoughts on this report? Let us know!

[github-actions]

Instruction budget: PASS

Head 8239be29bbdd5b1379c783c5080af5924999323c measured against base v0.25.1 (312836d), last release on the same runner, on cpython-3.12-x86_64 (3.12.3). Workflow run

Verdict	Path	Head Ir/op	Base Ir/op	Delta
new	l1_hit_backed	–	–	–
LOWER	l1_hit	2,880	13,132	-78.07%
LOWER	l2_hit	184,545	196,046	-5.87%
LOWER	l2_hit_async_metrics	184,583	195,681	-5.67%
LOWER	minimal_l1_hit	2,887	11,984	-75.91%
LOWER	secure_l1_hit	138,060	156,278	-11.66%
LOWER	serializer_default	52,773	64,588	-18.29%
LOWER	serializer_default_records	1,042,215	1,481,271	-29.64%
LOWER	serializer_encrypted	97,520	109,657	-11.07%
ok	byte_storage_store_40b	2,757	2,756	+0.04%
ok	byte_storage_store_64k	724,781	724,750	+0.00%
ok	file_set	86,706	86,867	-0.19%
ok	miss	242,299	242,054	+0.10%
ok	object_cache_put_full	198,690	198,512	+0.09%
ok	serializer_arrow	2,211,905	2,219,865	-0.36%
ok	serializer_auto	72,481	72,849	-0.51%
ok	serializer_orjson	24,837	24,876	-0.16%

A path fails at +1% or more against the base (+2% for serializer_orjson). This check is not required: a deliberate cost increase is accepted at merge. Method: docs/performance.md, Instruction budgets.

[27Bslash6]

@kody start-review

[kodus-27b]

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.