chore(deps): update first-party cachekit to 0.6.0

[cachekit-renovate-bot]

This PR contains the following updates:

Package	Type	Update	Change
cachekit-core	dependencies	minor	0.5.0 → 0.6.0
cachekit_storage	dependencies	minor	=0.4.0 → =0.6.0

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

cachekit-io/cachekit-core (cachekit-core)

v0.6.0

Compare Source

Features

• cache keyring per-tenant derivation at construction via TenantKeyring (LAB-1638) (#​71) (d3f0eb0)
• expose winning-key index via decrypt_indexed for rotation drain observability (LAB-1645) (#​73) (d834f74)

---

Configuration

📅 Schedule: (in timezone Australia/Sydney)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate.

[kodus-27b]

WHAT: A dependency version bump (cachekit-core 0.4.0 -> 0.5.0) was made without CVE/SCA evidence or a lockfile update. WHY: Dependency changes can introduce known vulnerabilities or supply-chain risk. HOW: Run an OSV/SCA scan (e.g., cargo audit) on the new version, include the results/advisory links in the PR description, and update Cargo.lock accordingly.

Kody rule violation: Validate new/updated dependencies for CVEs and supply-chain risk

Prompt for LLM

File rust/Cargo.toml:

Line 23:

WHAT: A dependency version bump (cachekit-core 0.4.0 -> 0.5.0) was made without CVE/SCA evidence or a lockfile update. WHY: Dependency changes can introduce known vulnerabilities or supply-chain risk. HOW: Run an OSV/SCA scan (e.g., cargo audit) on the new version, include the results/advisory links in the PR description, and update Cargo.lock accordingly.

_{Talk to Kody by mentioning @kody}

_{Was this suggestion helpful? React with 👍 or 👎 to help Kody learn from this interaction.}

​

​

[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!

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

• Validate Business Logic: Ask Kody to validate your code against business rules by adding a comment with the @kody -v business-logic command.

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

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]

WHAT: The dependency cachekit-core was bumped from 0.5.0 to 0.6.0 without any CVE/SCA evidence. WHY: New dependency versions may introduce known vulnerabilities or supply-chain risks. HOW: Run an OSV/SCA scan (e.g., cargo audit) on the new version and include the results/advisory links in the PR description, and ensure Cargo.lock is updated.

Kody rule violation: Validate new/updated dependencies for CVEs and supply-chain risk

Prompt for LLM

File rust/Cargo.toml:

Line 23:

WHAT: The dependency cachekit-core was bumped from 0.5.0 to 0.6.0 without any CVE/SCA evidence. WHY: New dependency versions may introduce known vulnerabilities or supply-chain risks. HOW: Run an OSV/SCA scan (e.g., cargo audit) on the new version and include the results/advisory links in the PR description, and ensure Cargo.lock is updated.

_{Talk to Kody by mentioning @kody}

_{Was this suggestion helpful? React with 👍 or 👎 to help Kody learn from this interaction.}

​

​