chore: release main - #99
Merged
Merged
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configurationConfiguration used: Repository: cachekit-io/cachekit-rs/.coderabbit.yaml Review profile: ASSERTIVE Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
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. Comment |
cachekit-release-bot
Bot
force-pushed
the
release-please--branches--main
branch
9 times, most recently
from
October 2, 2026 03:13
82a3821 to
dc5987e
Compare
cachekit-release-bot
Bot
force-pushed
the
release-please--branches--main
branch
from
October 2, 2026 11:50
dc5987e to
6afbb11
Compare
Contributor
Author
|
🤖 Created releases: 🌻 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤖 I have created a release beep boop
cachekit-macros: 0.9.0
0.9.0 (2026-10-02)
⚠ BREAKING CHANGES
..now fails:interop_keyreturnsInvalidKey, and#[cachekit]does not compile. Rename the segment; its keys become a full cache miss.Bug Fixes
cachekit-rs: 0.9.0
0.9.0 (2026-10-02)
⚠ BREAKING CHANGES
EncryptionLayer::new,EncryptionLayer::with_previous_keys,CacheKitBuilder::encryption_from_bytesandCacheKitBuilder::encryption_from_bytes_with_previous) now require keys of exactly 32 bytes, current and previous, and returnCachekitError::Configfor any other length. Callers that pass longer keys to a raw-bytes API, including hex keys decoded manually, now get an error at construction. Use exactly 32-byte keys, the only length every SDK accepts (openssl rand -hex 32), or pass the hex string to.encryption()or useCacheKit::from_env()...now fails:interop_keyreturnsInvalidKey, and#[cachekit]does not compile. Rename the segment; its keys become a full cache miss.Bug Fixes
Performance Improvements
Dependencies
This PR was generated with Release Please. See documentation.