chore(deps): upgrade cipherstash-client to 0.38.0, drop vendored stack-auth patch (CIP-3233)#409
chore(deps): upgrade cipherstash-client to 0.38.0, drop vendored stack-auth patch (CIP-3233)#409freshtonic wants to merge 1 commit into
Conversation
|
Warning Review limit reached
More reviews will be available in 42 minutes and 22 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (2)
📒 Files selected for processing (33)
✨ 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 |
…tack-auth patch (CIP-3233) Moves Proxy off the `vendor/stack-auth` `[patch.crates-io]` workaround and onto the current released cipherstash-client group, built against the fixed stack-auth. Background: 2.2.4 (PR #408) shipped the CIP-3233 access-key token-refresh fix via a vendored stack-auth patched on top of the 0.34.1-alpha.4 source. cipherstash-client 0.38.0 links stack-auth 0.38.0, which carries the same fix from crates.io, so the vendored copy and patch are no longer needed. Changes: - cipherstash-client / cipherstash-config / cts-common: 0.34.1-alpha.4 -> 0.38.0 (carries the API migration from PR #406's 0.37.0 upgrade; 0.37 -> 0.38 needed no further source changes) - Remove `[patch.crates-io] stack-auth = { path = "vendor/stack-auth" }`, the `exclude = ["vendor/stack-auth"]` workspace entry, and the vendor/stack-auth tree - stack-auth now resolves from crates.io (0.38.0); single version of the cipherstash-client group in the lock (zerokms-protocol 0.12.19) Verified: `cargo check --workspace`, `cargo clippy --workspace --all-targets`, and `cargo test --workspace --lib` (111 proxy unit tests) all pass. Integration tests need a live DB/ZeroKMS and were not run here.
256ad08 to
2e11f69
Compare
Summary
Moves Proxy off the
vendor/stack-auth[patch.crates-io]workaround and onto the current releasedcipherstash-clientgroup, built against the fixed stack-auth. This is the CIP-3233 follow-up cleanup.Background: 2.2.4 (#408) shipped the CIP-3233 access-key token-refresh fix via a vendored stack-auth, patched on top of the
0.34.1-alpha.4source thatcipherstash-client 0.34.1-alpha.4pinned.cipherstash-client 0.38.0linksstack-auth 0.38.0, which carries the same fix straight from crates.io — so the vendored copy and the patch are no longer needed.Changes
cipherstash-client/cipherstash-config/cts-common:0.34.1-alpha.4→0.38.0(the current published group). The API migration for the0.34 → 0.37jump is carried over from the (closed) feat: upgrade cipherstash-client to 0.37.0 #406 0.37.0 upgrade — same 10 source-file changes;0.37 → 0.38needed no further source changes.[patch.crates-io] stack-auth = { path = "vendor/stack-auth" }, theexclude = ["vendor/stack-auth"]workspace entry, and the entirevendor/stack-auth/tree.stack-authnow resolves from crates.io at 0.38.0 (registry source, verified in the lock). Single version of the whole cipherstash-client group;zerokms-protocolat0.12.19.Verification
cargo check --workspace— cleancargo clippy --workspace --all-targets— cleancargo test --workspace --lib— 111cipherstash-proxyunit tests passstack-auth(0.38.0, registry source); novendor/orpatch.crates-ioreferences remainNot run:
cipherstash-proxy-integrationtests (need a live Postgres + ZeroKMS; they fail here only withConnectionRefused). Please run the full integration suite in CI / with creds before merge.Notes
Closes the
cipherstash/proxyfollow-up line item on CIP-3233.