chore: release main by cachekit-release-bot[bot] · Pull Request #64 · cachekit-io/cachekit-rs

cachekit-release-bot · 2026-08-08T03:12:22Z

🤖 I have created a release beep boop

cachekit-macros: 0.8.0

0.8.0 (2026-09-28)

⚠ BREAKING CHANGES

intents: CacheKit::encrypted(url, key) is now CacheKit::secure(url, key), and the SecureCache accessor cache.secure() is now cache.secure_cache(). Migration: rename both call sites; behaviour, defaults and feature gates are unchanged.

Code Refactoring

intents: rename CacheKit::encrypted to CacheKit::secure (LAB-4651) (#82) (11802d9)

cachekit-rs: 0.8.0

0.8.0 (2026-09-28)

⚠ BREAKING CHANGES

intents: CacheKit::minimal now enables an in-process L1 cache (1000 entries, no stale-while-revalidate, no cross-process invalidation). A minimal read may serve an L1 entry for up to its 300 s TTL after another writer changed the value in Redis. Chain .no_l1() on the returned builder to restore read-through-every-time behaviour.
intents: CacheKit::encrypted(url, key) is now CacheKit::secure(url, key), and the SecureCache accessor cache.secure() is now cache.secure_cache(). Migration: rename both call sites; behaviour, defaults and feature gates are unchanged.

Features

encryption: keyring rotation — previous_master_keys + sequential decrypt (LAB-686) (#63) (8b9e7ac)
intents: CacheKit::io falls back to CACHEKIT_API_KEY via io_from_env (LAB-4647) (#86) (464b9d2)
observability: live read counters, auto-wired SaaS telemetry, tracing events (LAB-521) (#81) (afe77ad)
rs: surface rotation drain signal via decrypt_indexed (LAB-1678) (#74) (15b94cf)

Bug Fixes

cachekitio: reject reserved cache-key segments in request path (LAB-2878) (#76) (0ed7e1d)
intents: CacheKit::minimal enables L1 with SWR off per intent-preset contract (LAB-4644) (#85) (e0d4388)
serializer: own the msgpack decode depth bound and add a structural walk (LAB-2503) (#73) (306c1b1)

Code Refactoring

intents: rename CacheKit::encrypted to CacheKit::secure (LAB-4651) (#82) (11802d9)

Dependencies

The following workspace dependencies were updated
- dependencies
  - cachekit-macros bumped from 0.7.0 to 0.8.0

This PR was generated with Release Please. See documentation.

coderabbitai · 2026-09-11T03:56:06Z

Important

Review skipped

Bot user detected.

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

⚙️ Run configuration

Configuration used: Repository: cachekit-io/cachekit-rs/.coderabbit.yaml

Review profile: ASSERTIVE

Plan: Advanced

Run ID: 537c6e93-d350-4914-965a-06e028627188

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

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 · 2026-09-21T23:19:35Z

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 · 2026-09-23T09:11:43Z

@kody start-review

kodus-27b · 2026-09-23T09:23:28Z

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 · 2026-09-24T01:35:21Z

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 · 2026-09-25T13:36:27Z

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 · 2026-09-25T13:55:15Z

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.

cachekit-release-bot Bot added the autorelease: pending label Aug 8, 2026

cachekit-release-bot Bot assigned 27Bslash6 Aug 8, 2026