Repository navigation
chore(main): release 0.26.0 - #668
cachekit-release-bot[bot] wants to merge 2 commits into
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Instruction budget: FAILHead
A path fails at +1% or more against the base. This check is not required: a deliberate cost increase is accepted at merge. Method: |
7fb204a to
5834781
Compare
|
@kody start-review |
Code Review Completed! 🔥The code review was successfully completed based on your current configurations. Kody Guide: Usage and ConfigurationInteracting with Kody
Providing Context (Files & MCPs)Add these hints in your PR description (or a comment) to unlock deeper checks:
Current Kody ConfigurationReview OptionsThe following review options are enabled or disabled:
|
a30f531 to
3620c04
Compare
e131e24 to
8ee28e8
Compare
🤖 I have created a release beep boop
0.26.0 (2026-11-03)
⚠ BREAKING CHANGES
@cache(backend=None),@cache.local(), or any plaintext, non-interop decorator that finds no backend configured) times its TTLs and its stale-while-revalidate refresh on the OS monotonic clock that the Rust extension reads, not ontime.monotonic(). Patchingtime.monotonic(pytest'smonkeypatch, freezegun'sfreeze_timeortick) no longer expires its entries or brings a refresh due: a test that needs an entry gone callsfn.invalidate_cache(...)orfn.cache_clear(). Caches with a backend are unchanged.Features
Bug Fixes
Performance Improvements
This PR was generated with Release Please. See documentation.