chore: bump pg-core 0.5 → 0.6#156
Open
dobby-coder[bot] wants to merge 1 commit into
Open
Conversation
Bumps pg-core requirement from 0.5.0 to 0.6.0 (resolves 0.5.10 → 0.6.0 in the lockfile) in both [dependencies] and [dev-dependencies]. Upstream 0.6.0 (encryption4all/postguard pg-core-v0.6.0) bundles a ciphertext bounds-check security fix and migrates from bincode 1.3.3 to bincode-next 3.0.0-rc.13, which clears RUSTSEC-2025-0141 in the transitive graph. No cryptify source changes required; the public API surface used by this crate (Parameters, VerifyingKey, Unsealer, UnsealerStreamConfig, Sealer, SealerStreamConfig, TestSetup) is unchanged. Closes #155
![dobby-coder[bot]](https://avatars.githubusercontent.com/in/3365457?s=60&v=4){kind=small}
Contributor
Author
There was a problem hiding this comment.
Verified locally on chore/bump-pg-core-0.6.0:
cargo build --release✓cargo test— 86 passed, 0 failed ✓cargo clippy --all-targets— clean ✓cargo fmt --all -- --check✓- CI green (Build amd64/arm64, Rust quality)
Diff is a pure dependency bump (Cargo.toml + Cargo.lock); no source changes needed since the pg-core API surface used here is unchanged in 0.6.0. Transitive bincode 1.3.3 → bincode-next 3.0.0-rc.13 clears RUSTSEC-2025-0141 for this crate. rustls-pemfile advisory correctly called out as out of scope (transitive via irma).
LGTM — approving via auto-approval since this agent authored the PR.
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.
Summary
Bumps
pg-corerequirement0.5.0→0.6.0in both[dependencies]and[dev-dependencies](resolves0.5.10→0.6.0inCargo.lock).Upstream 0.6.0 (encryption4all/postguard pg-core-v0.6.0, released 2026-05-13) bundles:
bincode 1.3.3tobincode-next 3.0.0-rc.13(chore: migrate from bincode to bincode-next postguard#182), which removes the unmaintainedbincodecrate from the transitive graph and clearsRUSTSEC-2025-0141for this crate.No cryptify source changes required: the API surface used by this crate (
Parameters,VerifyingKey,Unsealer,UnsealerStreamConfig,Sealer,SealerStreamConfig,TestSetup) is unchanged in 0.6.0.randwas already at0.10.0onmain— the tracker issue listed it as outdated, but that row was stale. The intentional dev-dep aliasrand08 = { package = "rand", version = "0.8" }(for pg-core's Sealer/TestSetup RNG) is unchanged.Out of scope
RUSTSEC-2025-0134(rustls-pemfileunmaintained) — transitive viareqwest 0.11→irma 0.2.1.irmastill pinsreqwest 0.11, so this needs an upstreamirmabump.Verification
Local on
chore/bump-pg-core-0.6.0:cargo build✓cargo test— 86 passed, 0 failed ✓cargo fmt --all -- --check✓cargo clippy --all-targets✓Reviewer quickstart
Closes #155