Repository navigation
Move the runvil-harness pin to its new history - #214
Merged
Merged
Conversation
[Low impact] The reviewed changes appear safe to merge; no blocking issue was found.
|
The history of `runvil-harness` was written again, so the commit that this workspace pins has a new id. The four pins in the root `Cargo.toml` move from `732429962c5873458213bb0072a0828a40ee4fb6` to `5bca6f9fd9b398d5f221a5893570b8085bc283da`, and `Cargo.lock` follows. - In `Cargo.lock` only the `source` line of each of the 15 crates from that repository changes. No package changes version.
vinniefalco
temporarily deployed
to
github-pages
November 12, 2026 20:38 — with
GitHub Actions
Inactive
This branch was previously 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.
The history of cppalliance/runvil-harness was rebuilt so that it includes the plan and vibe records of the Engine and the Harness. Every commit there has a new id, so the commit this repository pins has to move.
What changed
Cargo.toml(runvil,harness-gateway-client,plugin-web,plugin-mcp) move from73242996to5bca6f9f, the current head ofrunvil-harness.Cargo.lockfollows: thesourceline of each of the 15 crates from that repository changes, and no package changes version.Why this is safe
The code at the two commits is the same. The new head differs from the old one only by files under
plan/andvibe/: 156 records and the folder's two ignore files. All 1,094 commits of the first history are in the new one with the same code, author, dates, and message.The old commit stays reachable in
runvil-harnessthrough the tagbefore-plan-records, somasterhere keeps building until this merges. The tag goes away after that.Verification
Run locally on Windows with the new pin, all passing:
cargo fmt --all --checkcargo clippyon both partitions, withCARGO_BUILD_WARNINGS=denycargo nextest run --lockedon both partitions: 795 passed and 347 passedcargo docon the workspace partition withRUSTDOCFLAGS="-D warnings", andworkshop-serverwith private itemscargo dylint --allcargo xtask tidy, which includes theharness_pinchecknode --test crates/workshop/ui/test/docs-claims.mjscargo deny check,cargo audit, and theringcheckcargo build --locked -p workshopSummary by CodeRabbit