deps: upgrade cipherstash-client to 0.35.0 and EQL to 2.3.0#394
Draft
freshtonic wants to merge 2 commits into
Draft
deps: upgrade cipherstash-client to 0.35.0 and EQL to 2.3.0#394freshtonic wants to merge 2 commits into
freshtonic wants to merge 2 commits into
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
Bump cipherstash-client, cipherstash-config and cts-common to 0.35.0, and CS_EQL_VERSION to the eql-2.3.0 release. 0.35.0 reworks the EQL types for the 2.3 payload format: - `EqlCiphertext` is now a `#[serde(tag = "k")]` enum (Encrypted / SteVec) and `identifier` is a method rather than a field. - `encrypt_eql` returns the new `EqlOutput` type (Store / Query). The encrypt path now carries `EqlOutput`; the decrypt path keeps `EqlCiphertext`. `EqlOutput` is not `Clone`, so `vec![None; n]` is replaced with iterator construction. - `EqlError::CouldNotDecryptDataForKeyset` gained a `source` field. - `IndexType::SteVec` gained a `mode` field. Rewrite the data_row tests to build wire messages programmatically from the new EQL 2.3.0 types instead of hardcoded payload bytes.
cipherstash-client 0.35.0 emits SteVec storage payloads (`k: "sv"`) with no top-level `c` field — the root ciphertext lives in `sv[0].c`. EQL 2.3.0's `eql_v2._encrypted_check_c` CHECK constraint required a top-level `c`, so every insert/update of an encrypted JSONB column was rejected (integration test `update_with_param_jsonb`). EQL 2.3.1 fixes `check_encrypted` to accept either `c` or `sv` at the root. Bump CS_EQL_VERSION to eql-2.3.1.
freshtonic
force-pushed
the
feat/bump-eql-and-cipherstash-client
branch
from
c5f1f80 to
0a55b23
Compare
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
1 participant
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.
Bump cipherstash-client, cipherstash-config and cts-common to 0.35.0, and CS_EQL_VERSION to the eql-2.3.0 release.
0.35.0 reworks the EQL types for the 2.3 payload format:
EqlCiphertextis now a#[serde(tag = "k")]enum (Encrypted / SteVec) andidentifieris a method rather than a field.encrypt_eqlreturns the newEqlOutputtype (Store / Query). The encrypt path now carriesEqlOutput; the decrypt path keepsEqlCiphertext.EqlOutputis notClone, sovec![None; n]is replaced with iterator construction.EqlError::CouldNotDecryptDataForKeysetgained asourcefield.IndexType::SteVecgained amodefield.Rewrite the data_row tests to build wire messages programmatically from the new EQL 2.3.0 types instead of hardcoded payload bytes.
Acknowledgment
By submitting this pull request, I confirm that CipherStash can use, modify, copy, and redistribute this contribution, under the terms of CipherStash's choice.