fix(ci): complete Ast import removal in verification/mod.rs and cargo fmt across crate#44
Merged
Merged
Conversation
… fmt across crate The previous fix-up commit (9435baa) removed `use z3::ast::{Ast, Bool};` from `src/verification/z3_integration.rs` but missed the identical line at `src/verification/mod.rs:81`. The coverage job (which builds with `--features z3-verify`) still hit `-D unused-imports` on it and failed. This commit: - Removes the surviving unused `Ast` import in `src/verification/mod.rs`. - Runs `cargo fmt --all` to clear the formatter diff the `test` job was exit-1-ing on (12 files, mostly struct-literal expansion + use-ordering; no semantic change). The `security` job was cancelled by a runner shutdown signal during the cargo-outdated install — likely transient runner timeout, not a code issue, and should pass once re-run.
The SHA 65c79d7... no longer resolves; actions/upload-artifact v4 now points to ea165f8d. This was the root cause of every Hypatia Security Scan red across the estate (tracked in hyperpolymath/hypatia#213).
This was referenced May 12, 2026
Merged
hyperpolymath
added a commit
to hyperpolymath/v3-templater
that referenced
this pull request
May 12, 2026
…covered from #57) (#58) Recovery cherry-pick of the bump from closed PR #57. The original PR was closed under the rationale that estate-wide CI failures dominated its red marks — that was correct about the failures being systemic, but closing the bump itself stranded the dependency update. Reapplying. The systemic CI cause ( SHA no longer resolves) is being fixed separately; see hyperpolymath/proof-of-work#44 and hyperpolymath/affinescript-vite#9. 🤖 Recovered by Claude Code.
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.
Summary
Closes the remaining Rust CI red on
mainafter #43 (steamworks 0.12.2 → 0.13.1):coveragejob was still failing witherror: unused import: Astatsrc/verification/mod.rs:81. The fix-up commit9435baaremoved the same import fromsrc/verification/z3_integration.rsbut missed this second occurrence. Removed.testjob was exit-1-ing oncargo fmt --check. Rancargo fmt --allacross the crate — 12 files reformatted, no semantic change (struct-literal expansion + use-ordering).The
securityjob was cancelled by an Actions runner shutdown signal during thecargo-outdatedinstall — looks transient, not code-related, and should pass on rerun.Test plan
cargo fmt --all -- --checkclean.cargo build --features z3-verifysucceeds.coverage,test, andsecurityRust CI jobs go green on this branch.