chore(orion): update scorpiofs to 0.4.0 - #2162
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 32d205df68
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| [[package]] | ||
| name = "scorpiofs" | ||
| version = "0.3.0" | ||
| version = "0.4.0" |
There was a problem hiding this comment.
Regenerate the scorpiofs lock entry
After bumping scorpiofs to 0.4.0, the lockfile still carries the old dependency edge under this package (Cargo.lock:7759 lists git-internal 0.4.1). The 0.4.0 manifest requires git-internal = "0.8.5" (source), so cargo build --locked/CI will either reject the stale lockfile or an unlocked build will rewrite it. Please regenerate Cargo.lock from the published 0.4.0 package so the scorpiofs dependency graph points at the already-locked 0.8.5 package.
Useful? React with 👍 / 👎.
Summary
scorpiofsdependency to0.4.0Cargo.lockWhy
Orion integrates the ScorpioFS crate directly and passes the CL subpath into its Antares mount flow.
Validation
scorpiofs 0.4.0was published and Cargo-verifiedbuck2 build //project/distribution:distributionsucceededNote
The configured TUNA Cargo mirror had not yet synced
0.4.0when the lockfile was updated. The lockfile checksum is the SHA-256 of the crates.io release package.