chore: bump pg-core 0.6.0 → 0.6.1#164
Merged
Merged
Conversation
Contributor
Author
There was a problem hiding this comment.
Reviewed (note: same bot identity opened the PR, so cannot self-approve).
Patch bump pg-core 0.6.0 → 0.6.1, plus transitive lockfile updates (windows-sys, socket2). CI is green across build (amd64/arm64), clippy, fmt, and tests. Dev-dep is bumped in lockstep so the integration test harness still resolves. The PR description correctly explains why the rand 0.8 dev-dep and the rustls-pemfile advisory are out of scope. LGTM — safe to merge from this agent's perspective.
rubenhensen
approved these changes
May 18, 2026
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.
Bumps
pg-corefrom 0.6.0 to 0.6.1 (patch).Closes #163.
Skipped from the scan
rand08dev-dep is pinned to 0.8 on purpose —pg_core::test::TestSetup/Sealerrequires the rand 0.8 RNG trait. Bumping it to 0.10 would break the integration test harness (seeCargo.tomlcomment aboverand08). Mainrand = "0.10.0"is already current.rustls-pemfileunmaintained): transitive with no fix path right now; not addressed here.Verification
cargo build✅cargo test✅ (87 passed)cargo clippy --all-targets✅ (no warnings)cargo fmt --all -- --check✅Reviewer quickstart