Repository navigation
fix(deps): remediate Rust dependency advisories - #198
Open
richardgetz wants to merge 1 commit into
Open
richardgetz wants to merge 1 commit into
richardgetz wants to merge 1 commit into
Conversation
This branch has not been deployed
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.
This change clears the active dependency findings reported by cargo-deny without changing its policy.
quinn-prototo 0.11.18, the patched release used by the tunnel dependency path.rustlsto 0.23.46.zipto 9.0.4 and adapt the affected archive consumers.serde_yaml’s unmaintainedunsafe-libyamlimplementation with the maintainedyaml_serdepackage via the existingserde_yamlimport name.The keyring migration keeps the current Linux native backend selection, keyutils plus Secret Service persistence, and its existing fallback semantics. It retains the same service, account, target and application identifiers, so existing stored records continue to be addressed through the same keyring interface. The macOS Keychain ACL implementation and platform selection are unchanged. No user credentials were read or modified.
Validation:
cargo deny --log-level warn --manifest-path ./codex-rs/Cargo.toml --all-features check— advisories, bans, licenses and sources all pass.just test -p codex-keyring-store preserves_typed_causes_without_guessing_from_messages— 1 passed on macOS.just test -p codex-tui motion::tests— 2 passed on macOS.just test -p codex-core-plugins curated_plugin_zip_extraction_strips_privileged_permission_bits— 1 passed, 479 skipped on macOS; compiled the updated ZIP consumer and exercised Unix privileged-bit stripping.cargo check -p codex-keyring-store -p codex-rmcp-client -p codex-tuipassed on Ubuntu 24.04 with Rust 1.95.0 in run 39053341869. The job later stopped at a missing nextest installation before running tests; the compile/check step itself passed.cargo-nextest 0.9.103and verified its checksum. Nextest also reported that.config/nextest.tomlkeyprofile.local.inheritsis unknown to this version; this nonfatal warning did not prevent either selected test from running.540bbabc1cbf0a20d4cf4bc790c0ae5b257e4731. The source-parity gate passed and confirmed the proof branch differs from the PR source only in the existing.github/workflows/rust-ci.yml; that temporary proof change is not part of this PR. The proof job used one Ubuntu runner withcontents: read, no secrets and no matrix.just bazel-lock-update, finaljust fmt, andgit diff --check origin/stablepassed.The TUI adapter uses zbus 6’s
OwnedVariantAPI. Fork Delta Inventory: no entry is needed; this change adds no fork-only behavior. Workflow cleanup PR #197 remains separate.