[BUG] Tracked lockfile does not follow the selected immutable manifest graph #3
Labels
No labels
alpha-1
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/boot-tool#3
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Tracked lockfile does not follow the selected immutable manifest graph. Maintained validation cannot reach its intended successful boundary.
Reproduction
At the linked source revision, use the maintained exact Git dependency helper and run cargo build --locked with the workflow toolchain. The original failing source and current repairs are distinct; failures and true exit statuses are retained.
Expected and actual behavior
The maintained source should compile, discover its original controls and complete the specified checks without warnings. The manifest selects newer real Git dependency commits while Cargo.lock still records the previous graph. A locked build refuses to update its input and exits before compilation.
Environment and identity
Evidence and prior checks
Generate the tracked lockfile from the actual selected manifest graph with explicit canonical Git inputs and registry denial. Preserve --locked and the CI guard. The signed manifest and lockfile fix is 30a83cd5; exact-head CI and warning review are tracked independently.
Tests and exact-head CI now run in parallel with implementation. A skipped, pending or unrun check is not a pass; independent source work continues while regressions are repaired.
Tracking
Phase completion tracks the full remaining goal. Signed source fixes, coherent dependency adoption and exact validation results will be recorded before closure.