Skip to content

fix(deps): bump cipherstash-client, cipherstash-config, and cts-common to 0.42.2 - #456

Merged
tobyhede merged 1 commit into
mainfrom
fix-cip-3815-jsonwebtoken-patch
Aug 18, 2026
Merged

fix(deps): bump cipherstash-client, cipherstash-config, and cts-common to 0.42.2#456
tobyhede merged 1 commit into
mainfrom
fix-cip-3815-jsonwebtoken-patch

Conversation

@tobyhede

Copy link
Copy Markdown
Contributor

Pulls in stack-auth 0.42.2, which bumps jsonwebtoken from 9.3.1 to 10.4.0.

…n to 0.42.2

Pulls in stack-auth 0.42.2, which bumps jsonwebtoken from 9.3.1 to 10.4.0.

Signed-off-by: Toby Hede <toby@cipherstash.com>

@freshtonic freshtonic left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving.

Cargo.toml and Cargo.lock are consistent, and the full test matrix (PostgreSQL 14–17) plus the performance regression check are green.

The part of this worth stating explicitly, since the PR body describes it only as a version bump: jsonwebtoken 9.3.1 → 10.4.0 swaps the crypto backend from ring to aws-lc-rs (stack-auth 0.42.2 requests default-features = false, features = ["aws_lc_rs", "use_pem"]). For a service that builds release/Docker images this is the kind of change that can break a build without touching a test — but it's safe here: aws-lc-rs/aws-lc-sys are already in the lock on main via rustls, so the build environment already carries the C/CMake toolchain and nothing new is introduced.

Also carried along, both consistent with the 0.42.2 line: zeroize 1.8.1 → 1.9.0 (plus zeroize_derive 1.4.2 → 1.5.0) and zerokms-protocol 0.12.26 → 0.12.28.

@tobyhede
tobyhede merged commit 0f31273 into main Aug 18, 2026
5 checks passed
@tobyhede
tobyhede deleted the fix-cip-3815-jsonwebtoken-patch branch August 18, 2026 05:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants