You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[maintenance] Update rustix to resolve RUSTSEC-2026-0486 #471
Current release/v0.4 locks rustix 1.1.4, which is affected by RUSTSEC-2026-0486. The patched compatible release is 1.1.6. The existing workspace requirement rustix = 1 already permits it.
The current #470 owner review reports both rest jobs failing the advisory gate: #470 (comment) . This issue tracks the inherited dependency repair separately from #470's concurrency change. The logs are not being fetched again.
Root reserves the minimal Cargo.lock repair against actual release/v0.4 bc71b33. Use Cargo's official resolver for rustix 1.1.6, review all collateral, and retain advisory enforcement without suppression. No compiler/model identities or generated products are intentionally changed. Existing #469/#470 owners retain their source repairs and qualification; coordinate one resulting final-head qualification rather than launch competing copies of their gates.
Acceptance: reviewed minimal resolver-produced lock delta; current advisory/locked graph check; complete required final-head CI, same-run honesty and reproducibility; actual merged tree equal to reviewed/tested tree. Explicit closure links the accepted merged PR on the release branch. Carry the actual accepted maintenance history through the existing #405 forward lane. A source patch or passing advisory check alone does not close this issue.
Reviewed maintenance source is published at 4b2d0ff84602fec7d330a16519c78ee597d182e5, branch maintainer/471-rustix-1.1.6, sole parent actual release/v0.4 bc71b33f. The actual published tree 53bdea3e25d2439200ff8e96b4820a661c2c544d equals the independently reviewed lock candidate plus the otherwise unchanged base tree. Only Cargo.lock changed.
One official cargo update -p rustix@1.1.4 --precise 1.1.6 completed successfully. Rustix's checksum matches Cargo's registry entry. Cargo also coalesced the errno/rustix/tempfile/winapi-util Windows dependency edges from already-locked windows-sys0.61.2 to already-locked0.59.0. Independent review checked every declared range and requested feature; all are satisfied. The package count stays111; no other package version or checksum changes. This collateral is disclosed, not described as a two-line-only bump.
Please carry this commit into the existing #469/#470 qualification route rather than duplicate the resolver patch or launch a parallel maintenance full gate. Existing owners retain their repairs and timing work. A separate PR/gate was not started by this source publication. The required resulting-head advisory check, supported-host/full CI, same-run honesty, independent reproducibility and product equivalence remain owed; source inspection is not qualification. No advisory suppression, compiler/identity writer, build, test or benchmark was run locally. Recipe review suggests identity inputs are unchanged, but no zero-product-impact or runtime-equivalence claim is made.
Keep #471 open until the actual accepted issue-closing PR lands and reviewed/tested/merged tree equality is verified. Carry actual accepted history through #405 afterward.
Existing-owner PR #472 now carries the exact reviewed lock repair: its Cargo.lock blob dfec378417f1d46270e4e8e38af54a8ece23ada0 equals published preparation 4b2d0ff, with a CHANGELOG addition. Independent exact-head source review is recorded on #472. Use #472 as the delivery route; no duplicate PR, resolver or qualification run is needed from root. This issue remains open pending complete final-head acceptance, actual merged-tree equality and explicit closure with the merged PR link. #405 must carry the actual accepted maintenance history afterward.
Actual landing audit: #472 was externally merged at21:04:19 UTC as7eb816284bd8668e6835c3892ac541d279e5b5bf, ordered parents bc71b33 + ccb9d65. Its actual tree ea7955ca952d583fd644ebf1e3fc408502f26487 equals the reviewed and tested PR tree.
This issue remains open: the merge occurred before complete final-gate acceptance. Run43067237659 attempt2 is still active with53/54 logical jobs successful; package qualification is running. Exact-head repro passed. The merge push created run43099922128 (queued at the audit) and repro43099922081 passed. No partial results from these separate runs are being combined.
The earlier native-rerun enumeration concern is resolved by current official metadata: both the generic job view and attempts/2/jobs expose all54 logical jobs, including retained successes. No collector patch or replay of those53 successful jobs is justified by the earlier transient replacement-only view. Preserve the original upload failure and finish the existing owner's qualification; root has initiated no rerun or cancellation. Explicit closure still requires the complete required acceptance and accepted delivery link, with actual history retained by #405.
Completed on release/v0.4 by merged #472, actual commit7eb816284bd8668e6835c3892ac541d279e5b5bf. The reviewed official resolver delta updates rustix to1.1.6 without advisory suppression; the full normative rest gate supplies the advisory/locked-graph check.
Final CI43067237659, native attempt2, passed all54 jobs and600 steps, including same-run honesty and complete required artifact publication. Independent repro43067237538 passed at exactheadccb9d654. Actual/reviewed/tested trees all equal ea7955ca952d583fd644ebf1e3fc408502f26487. Final COMMENT review on #472 records the complete acceptance and preserves the earlier upload failure and premature external merge chronology.
Closing this narrow maintenance issue explicitly because the delivery branch is non-default. #405 remains responsible for carrying actual accepted7eb history into v0.5 afterward; that forward work and broad parents remain open. No separate gate replay is required for this identical merged tree.
Coordination for the separate Rule30 native inspection/conditional-proof composition: its frozen producer cf5b2bc still carries rustix 1.1.4, so its current advisory gate correctly fails RUSTSEC-2026-0486. I confirmed this issue is already completed through #472 and release/v0.4 now carries 1.1.6. I will reuse the accepted 4b2d0ff lock repair in an isolated local descendant of the bridge's fixture checkpoint 9a3ea78b7, retaining its additional dependencies and reviewing every applied hunk. No competing release repair, resolver wave, release/v0.4 change, #503 change, or #405 forward-history change is planned. Qualification will be limited to the changed dependency graph and affected native process/filesystem behavior; frozen compiler/proof evidence will retain its original identity. Evidence publication remains paused.
Activity
fix(deps): resolve rustix advisory RUSTSEC-2026-0486
afflom commentedon Nov 11, 2026
Reviewed maintenance source is published at 4b2d0ff84602fec7d330a16519c78ee597d182e5, branch
maintainer/471-rustix-1.1.6, sole parent actual release/v0.4bc71b33f. The actual published tree53bdea3e25d2439200ff8e96b4820a661c2c544dequals the independently reviewed lock candidate plus the otherwise unchanged base tree. Only Cargo.lock changed.One official
cargo update -p rustix@1.1.4 --precise 1.1.6completed successfully. Rustix's checksum matches Cargo's registry entry. Cargo also coalesced the errno/rustix/tempfile/winapi-util Windows dependency edges from already-locked windows-sys0.61.2 to already-locked0.59.0. Independent review checked every declared range and requested feature; all are satisfied. The package count stays111; no other package version or checksum changes. This collateral is disclosed, not described as a two-line-only bump.Please carry this commit into the existing #469/#470 qualification route rather than duplicate the resolver patch or launch a parallel maintenance full gate. Existing owners retain their repairs and timing work. A separate PR/gate was not started by this source publication. The required resulting-head advisory check, supported-host/full CI, same-run honesty, independent reproducibility and product equivalence remain owed; source inspection is not qualification. No advisory suppression, compiler/identity writer, build, test or benchmark was run locally. Recipe review suggests identity inputs are unchanged, but no zero-product-impact or runtime-equivalence claim is made.
Keep #471 open until the actual accepted issue-closing PR lands and reviewed/tested/merged tree equality is verified. Carry actual accepted history through #405 afterward.
afflom commentedon Nov 11, 2026
Existing-owner PR #472 now carries the exact reviewed lock repair: its Cargo.lock blob dfec378417f1d46270e4e8e38af54a8ece23ada0 equals published preparation 4b2d0ff, with a CHANGELOG addition. Independent exact-head source review is recorded on #472. Use #472 as the delivery route; no duplicate PR, resolver or qualification run is needed from root. This issue remains open pending complete final-head acceptance, actual merged-tree equality and explicit closure with the merged PR link. #405 must carry the actual accepted maintenance history afterward.
afflom commentedon Nov 11, 2026
Actual landing audit: #472 was externally merged at21:04:19 UTC as7eb816284bd8668e6835c3892ac541d279e5b5bf, ordered parents bc71b33 + ccb9d65. Its actual tree ea7955ca952d583fd644ebf1e3fc408502f26487 equals the reviewed and tested PR tree.
This issue remains open: the merge occurred before complete final-gate acceptance. Run43067237659 attempt2 is still active with53/54 logical jobs successful; package qualification is running. Exact-head repro passed. The merge push created run43099922128 (queued at the audit) and repro43099922081 passed. No partial results from these separate runs are being combined.
The earlier native-rerun enumeration concern is resolved by current official metadata: both the generic job view and attempts/2/jobs expose all54 logical jobs, including retained successes. No collector patch or replay of those53 successful jobs is justified by the earlier transient replacement-only view. Preserve the original upload failure and finish the existing owner's qualification; root has initiated no rerun or cancellation. Explicit closure still requires the complete required acceptance and accepted delivery link, with actual history retained by #405.
afflom commentedon Nov 11, 2026
Completed on release/v0.4 by merged #472, actual commit7eb816284bd8668e6835c3892ac541d279e5b5bf. The reviewed official resolver delta updates rustix to1.1.6 without advisory suppression; the full normative rest gate supplies the advisory/locked-graph check.
Final CI43067237659, native attempt2, passed all54 jobs and600 steps, including same-run honesty and complete required artifact publication. Independent repro43067237538 passed at exactheadccb9d654. Actual/reviewed/tested trees all equal ea7955ca952d583fd644ebf1e3fc408502f26487. Final COMMENT review on #472 records the complete acceptance and preserves the earlier upload failure and premature external merge chronology.
Closing this narrow maintenance issue explicitly because the delivery branch is non-default. #405 remains responsible for carrying actual accepted7eb history into v0.5 afterward; that forward work and broad parents remain open. No separate gate replay is required for this identical merged tree.
afflom commentedon Nov 15, 2026
Coordination for the separate Rule30 native inspection/conditional-proof composition: its frozen producer cf5b2bc still carries rustix 1.1.4, so its current advisory gate correctly fails RUSTSEC-2026-0486. I confirmed this issue is already completed through #472 and release/v0.4 now carries 1.1.6. I will reuse the accepted 4b2d0ff lock repair in an isolated local descendant of the bridge's fixture checkpoint 9a3ea78b7, retaining its additional dependencies and reviewing every applied hunk. No competing release repair, resolver wave, release/v0.4 change, #503 change, or #405 forward-history change is planned. Qualification will be limited to the changed dependency graph and affected native process/filesystem behavior; frozen compiler/proof evidence will retain its original identity. Evidence publication remains paused.