deps(deps): bump serde from 1.0.228 to 1.0.229 - #58
Conversation
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
🔒 Security Validation ReportGenerated: Mon Jul 20 10:58:49 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: Mon Jul 20 11:01:20 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. |
Bumps [serde](https://github.com/serde-rs/serde) from 1.0.228 to 1.0.229. - [Release notes](https://github.com/serde-rs/serde/releases) - [Commits](serde-rs/serde@v1.0.228...v1.0.229) --- updated-dependencies: - dependency-name: serde dependency-version: 1.0.229 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
767b9ca to
fc87745
Compare
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
🔍 Pull Request SummaryGenerated: Tue Jul 28 21:58:04 UTC 2026 📋 Validation Results
❌ Overall Status: FAILED🔒 Security Checklist
📝 Review NotesPlease review the security implications of this change carefully. ❌ Automated validation failed! Please address the issues above before merging. |
🔒 Security Validation ReportGenerated: Tue Jul 28 21:58:13 UTC 2026 📊 Summary
❌ Overall Security Status: FAILEDCritical security validations failed. Please review the issues above. 🔍 DetailsThis report covers:
📋 Next Steps❌ Security issues detected. Please address before deployment. ❌ Security validation failed! Please address security issues before merging. |
…#68) 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.
Bumps serde from 1.0.228 to 1.0.229.
Release notes
Sourced from serde's releases.
Commits
7fc3b4cRelease 1.0.2296d6e9a1Merge pull request #3085 from dtolnay/syn36dec3b7Update to syn 3cfe6692Resolve mut_mut pedantic clippy lint1023d07Update actions/upload-artifact@v6 -> v7dd682c2Update actions/checkout@v6 -> v75f0f18bUpdate ui test suite to nightly-2026-06-0163a1498Regenerate stderr with trybuild normalization fixesfa7da4aFix unused_features warning6b1a178Unpin CI miri toolchain