Skip to content

chore(deps): bump hickory to 0.26.3 for RUSTSEC-2026-0506..0520 - #9394

Merged
TheSentinel454 merged 1 commit into
mainfrom
elrond/hickory-0262
Nov 12, 2026
Merged

TheSentinel454 merged 1 commit into
mainfrom
elrond/hickory-0262

Conversation

@TheSentinel454

Copy link
Copy Markdown
Contributor

What

Lockfile-only bump of hickory-net, hickory-proto and hickory-resolver from 0.26.1/0.26.2 to 0.26.3.

Why

New advisories (RUSTSEC-2026-0506 through 0520) against hickory-net and hickory-resolver < 0.26.2 fail cargo-deny check in the Security job. Every main commit since 14:21 UTC today is red, so the Docker workflow's "Qualify relay image source" step refuses to publish relay images.

Testing

cargo-deny check locally: advisories ok, bans ok, licenses ok, sources ok.

What got simpler

Nothing; dependency bump.

🤖 Generated with Claude Code

The new hickory-net and hickory-resolver advisories fail cargo-deny's
Security job on every main commit since 14:21 UTC, which blocks the
relay image's same-SHA CI qualification. Lockfile-only bump.

Co-authored-by: Elrond <28d6302a099e5225b02c4155ac4236e4912603df2ab08dbfc2f4fef08ce598c8@buzz.block.builderlab.xyz>
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Signed-off-by: Luke Tornquist <[email protected]>
@TheSentinel454
TheSentinel454 requested a review from a team as a code owner November 12, 2026 15:03
@github-actions github-actions Bot added the codex-security-review-current The posted Codex security review matches its recorded range. label Nov 12, 2026
@github-actions

Copy link
Copy Markdown

🔐 Codex Security Review

Note: This is an automated, security-focused review generated by Codex.
Use it as a supplement to human review; false positives are possible.

Scope

  • Exact PR diff: 68785206041813cd10a25f2898f26ff9c85fc927...8d80c136feda54de64bb1153c285a1bfbbb8a97e
  • Model: gpt-6.1-sol

💡 Click "edited" above to see earlier reviews for this PR.


Review Summary

Overall Risk: NONE

No concrete security, correctness, or reliability findings in the authorized lockfile-only changes. Dependency references remain internally consistent.

Findings

No concrete security, correctness, or reliability findings were identified.

Notes

  • Review used read-only inspection. Updated dependency sources were unavailable locally; builds, tests, and network verification were not performed.

Generated by Codex Security Review |
Requested by: @TheSentinel454 |
Workflow run

@kazemek21 kazemek21 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.

Kyle reviewed the PR and the Nexus review-tracker notes and approved with no comments.

Posted by Codex (gpt-6.1-sol) on behalf of kylez.

@TheSentinel454
TheSentinel454 merged commit 0c58b33 into main Nov 12, 2026
96 of 98 checks passed
@TheSentinel454
TheSentinel454 deleted the elrond/hickory-0262 branch November 12, 2026 18:14
ravarora2 added a commit that referenced this pull request Nov 12, 2026
Co-authored-by: dessert <7d616e7e143e5d408159614dccff1371350a1c1bd36c8de838a45ece5aca0aca@buzz.block.builderlab.xyz>

* origin/main:
  buzz-db: pin explicit FK-child cleanup and same-workflow fire links (#8317)
  chore(deps): bump hickory to 0.26.3 for RUSTSEC-2026-0506..0520 (#9394)

Signed-off-by: Ravneet Arora <[email protected]>
wesbillman added a commit that referenced this pull request Nov 12, 2026
Integrate #9394 without changing the reviewed mobile implementation.

Co-authored-by: Brain <1a02c72794dcd0f07058a353bc3a81f4028b8c77c92c87fce6d5c8b85970a20b@buzz.block.builderlab.xyz>
Signed-off-by: Wes <[email protected]>

This branch was successfully deployed

1 active deployment
codex-review — 8d80c136 Deployed Nov 12, 2026 by TheSentinel454 via Run Codex Security Review #14590
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

codex-security-review-current The posted Codex security review matches its recorded range.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants