deps: bump serde 1.0.229 + serde_json 1.0.151 (supersedes #58, #57) - #68
Merged
Conversation
Supersedes dependabot PRs #58 and #57, which were both Cargo.lock-only but had gone stale: five other dependency bumps landed on `main` first, so their locks no longer applied and GitHub reported #58 CONFLICTING. Regenerating both on current `main` with `cargo update --precise` is equivalent to what those PRs did and avoids waiting on a dependabot rebase cycle. serde pulls its workspace-internal companions with it (serde_core, serde_derive 1.0.228 -> 1.0.229); that is the normal coupled set, not extra scope. Lockfile-only: no Cargo.toml, no source, no API change. Note for the record: #57 previously showed a red Test Matrix, and it was NOT caused by this bump. It failed on a flaky wall-clock assertion in lib-q-k12/tests/constant_time.rs at merge-base 123fc27, before `min_time` (repeated-measurement minimum) existed on main.
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
This was referenced Jul 28, 2026
🔒 Security Validation ReportGenerated: Tue Jul 28 22:47:54 UTC 2026 📊 Summary
✅ Overall Security Status: PASSEDAll critical security validations passed successfully. 🔍 DetailsThis report covers:
📋 Next Steps✅ Security validation passed. Code is ready for deployment. ✅ Security validation passed! This code meets all security requirements. |
🔍 Pull Request SummaryGenerated: Tue Jul 28 22:50:27 UTC 2026 📋 Validation Results
✅ Overall Status: PASSED🔒 Security Checklist
📝 Review NotesPlease review the security implications of this change carefully. ✅ Automated validation passed! This PR is ready for review. |
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.
Supersedes #58 and #57, which were Cargo.lock-only but went stale after five other bumps landed on
main(#58 was reported CONFLICTING). Regenerated on currentmainwithcargo update --precise.Lockfile-only: no Cargo.toml, no source, no API change.
Note: #57's earlier red Test Matrix was not caused by this bump - it was a flaky wall-clock assertion in
lib-q-k12/tests/constant_time.rs, addressed separately.