Skip to content

fix(security): update ruint past RUSTSEC-2026-0220 - #522

Merged
proerror77 merged 1 commit into
mainfrom
codex/ruint-rustsec-521
Jul 30, 2026
Merged

fix(security): update ruint past RUSTSEC-2026-0220#522
proerror77 merged 1 commit into
mainfrom
codex/ruint-rustsec-521

Conversation

@proerror77

@proerror77 proerror77 commented Jul 30, 2026

Copy link
Copy Markdown
Owner

Change contract

Resolve ruint at patched version 1.20.0 so required Cargo audit no longer
reports RUSTSEC-2026-0220, without changing runtime code or dependency
features.

Issue relationship

Closes #521

Out of scope

Polymarket Gate/rollback behavior, CI restructuring, other dependency upgrades,
production mutation, research, snapshot/#235, evaluator/MCTS, and artifacts.

Dependency or merge order

Merge this PR before rebasing PR #520 onto the resulting exact main.

Focused validation

  • Existing cargo audit --json: RED on RUSTSEC-2026-0220 / ruint 1.19.0.
  • Updated cargo audit --json: PASS with zero vulnerabilities.
  • cargo metadata --locked --format-version 1 --no-deps: PASS.
  • cargo test --locked -p hft-data-adapter-polymarket -p hft-execution-adapter-polymarket: 61 passed, 0 failed, 1 ignored.
  • git diff --check: PASS.

Rollout/rollback impact

No production rollout. Roll back by reverting this two-line lockfile resolution
change; doing so reintroduces the advisory and required audit failure.

@proerror77
proerror77 enabled auto-merge (squash) July 30, 2026 19:39
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

@coderabbitai

coderabbitai Bot commented Jul 30, 2026

Copy link
Copy Markdown

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (1)
  • rust_hft/Cargo.lock is excluded by !**/*.lock

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 2f45916e-6867-4a6c-ac29-be770fc7d173

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@proerror77
proerror77 merged commit 3896eed into main Jul 30, 2026
47 of 48 checks passed
@proerror77
proerror77 deleted the codex/ruint-rustsec-521 branch July 30, 2026 20:07
proerror77 pushed a commit that referenced this pull request Aug 1, 2026
…s lockfile

PR #522 updated only the main workspace lock; ploy-ci's Dependency
audit scans rust_hft/prediction-markets/Cargo.lock and now fails
repo-wide on lanes that trigger it.

Closes #561
proerror77 added a commit that referenced this pull request Aug 1, 2026
…onfig pins (#562)

* fix(security): bump ruint past RUSTSEC-2026-0220 in prediction-markets lockfile

PR #522 updated only the main workspace lock; ploy-ci's Dependency
audit scans rust_hft/prediction-markets/Cargo.lock and now fails
repo-wide on lanes that trigger it.

Closes #561

* test(ploy): update tape config pins for Binance kinds and tick-level sampling

The scope-gated CI let #550/#548 merge without running
workspace_runtime_retirement; its pinned include_kinds and
quote_sample_ms went stale.

Refs #540
Refs #539

* fix(research): refresh checked-in Linux policy graph for ruint bump

The build.rs graph validator requires input:Cargo.lock to hash the
workspace lockfile exactly; the ruint bump changed it. ruint itself is
not in the Linux policy package set, so only the input line and the
canonical fingerprint need refreshing.

Refs #561

* test(research): re-pin mission templates to refreshed policy snapshot id

The policy snapshot id is derived from the dependency fingerprint;
the ruint lockfile refresh changed it, so the checked-in BTC/SOL
mission templates must be re-pinned.

Refs #561

---------

Co-authored-by: Sonic Shih <sonic.shih@mandonothing.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

fix(security): update ruint past RUSTSEC-2026-0220

1 participant