Repository navigation
Conversation
cachekit-core 0.7.1 seals native AES-256-GCM encryption in one pre-sized buffer: one allocation and one plaintext copy instead of three. The CLI reaches that path through cachekit-rs's encryption layer. Output bytes and the wire format are unchanged.
Contributor
Author
|
@kody start-review |
This branch has not been deployed
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.
What
Moves
Cargo.lockfrom cachekit-core 0.7.0 to 0.7.1. The diff is thecachekit-corelock entry only: version and checksum.Cargo.tomlis unchanged, since"0.7"already admits 0.7.1.cargo metadata --lockedaccepts the lockfile on both stable and the 1.85 rust-version toolchain, andcargo test --lockedpasses.cargo update -p cachekit-core --precise 0.7.1also re-unifies four Windows-onlywindows-sysreferences from 0.52 to 0.61. That churn is unrelated to this bump, so it is left out.Why
cachekit-core 0.7.1 (cachekit-io/cachekit-core#127) seals native
encrypt_aes_gcmin one pre-sized buffer: one allocation and one plaintext copy instead of three.ckreaches it through cachekit-rs's encryption layer. Output bytes and the wire format are unchanged;derive_domain_keyis untouched.The commit type is
perfso release-please lists it and the binary ships it; achore(deps)lockfile bump would cut no release.