Fix release qualification after an already-green merge #478

Merged
buildagent merged 1 commit from fix/release-ci-parent-evidence into master 2026-10-31 22:56:32 +01:00
Member

A version-only release after a normal merge can pass CI classification, yet publication refuses the same source: the parent's jobs were skipped as already green, and the release gate never searches the parent's identical-tree qualification. This blocked v0.41.26 before publication (failed gate).

Reuse the existing tree matcher with an explicit root for the version-only parent. The gate now composes one strictly validated version-only edge with tree equality. It does not recursively follow another version bump. Real executed success rows are still required; own failures, matching-tree failures, cancellations and unreadable API responses retain their existing precedence.

The regression reproduces the failed publication shape, then checks successful inheritance and four failure-precedence cases. All 57 CI path/promotion tests and five CI API gate tests pass, along with targeted clippy, formatting and shell syntax checks. The regression fails against the original gate. Runtime source, dependency pins, guest inputs, ABI and performance limits are unchanged; the qualified runtime and fresh performance evidence from #476 remain intact.

A version-only release after a normal merge can pass CI classification, yet publication refuses the same source: the parent's jobs were skipped as already green, and the release gate never searches the parent's identical-tree qualification. This blocked v0.41.26 before publication ([failed gate](https://git.h-dv.de/h-dv/code-index/actions/runs/2018)). Reuse the existing tree matcher with an explicit root for the version-only parent. The gate now composes one strictly validated version-only edge with tree equality. It does not recursively follow another version bump. Real executed success rows are still required; own failures, matching-tree failures, cancellations and unreadable API responses retain their existing precedence. The regression reproduces the failed publication shape, then checks successful inheritance and four failure-precedence cases. All 57 CI path/promotion tests and five CI API gate tests pass, along with targeted clippy, formatting and shell syntax checks. The regression fails against the original gate. Runtime source, dependency pins, guest inputs, ABI and performance limits are unchanged; the qualified runtime and fresh performance evidence from #476 remain intact.
fix: preserve qualified parent tree evidence in release gates
All checks were successful
Package CI / package-corpus (php) (pull_request) Successful in 29s
Package CI / package (svelte) (pull_request) Successful in 36s
Package CI / package-corpus (javascript) (pull_request) Successful in 38s
Package CI / package-corpus (python) (pull_request) Successful in 32s
Package CI / package (xaml) (pull_request) Successful in 37s
Package CI / package-corpus (rust) (pull_request) Successful in 32s
Package CI / package-corpus (svelte) (pull_request) Successful in 33s
Package CI / package-corpus (typescript) (pull_request) Successful in 34s
Package CI / package-corpus (ruby) (pull_request) Successful in 39s
Package CI / package-corpus (vue) (pull_request) Successful in 32s
Package CI / package-corpus (xaml) (pull_request) Successful in 32s
Package CI / package-corpus (timeline) (pull_request) Successful in 43s
Package CI / package overhead budgets (nightly, one package at a time) (pull_request) Has been skipped
CI / guest crates (fmt, clippy, doc) (pull_request) Successful in 53s
CI / CI lane wall-clock headroom (pull_request) Successful in 1m4s
Pilot plugin compatibility / Fetch the pinned runtime once (pull_request) Successful in 1m51s
Pilot plugin compatibility / Pilot compatibility (csharp) (pull_request) Successful in 1m4s
Pilot plugin compatibility / Pilot compatibility (timeline) (pull_request) Successful in 1m19s
Pilot plugin compatibility / Pilot compatibility result (pull_request) Successful in 1s
CI / cargo doc (intra-doc links) (pull_request) Successful in 8m40s
CI / cargo deny (pull_request) Successful in 9m8s
CI / cargo clippy (pull_request) Successful in 10m12s
CI / cargo check (MSRV 1.99.1) (pull_request) Successful in 12m42s
CI / cargo test (abi, 32-bit + wasm32) (pull_request) Successful in 12m39s
CI / cargo check (windows-gnu) (pull_request) Successful in 13m31s
CI (Windows) / fmt + clippy + build + test (windows) (pull_request) Successful in 52m36s
CI / OSS corpus (tier 1) (pull_request) Successful in 1h43m14s
CI / cargo test (pull_request) Successful in 2h0m9s
CI / cargo test (daemon transport) (pull_request) Successful in 9m27s
CI / Plugin path cost + pool throughput (nightly) (pull_request) Has been skipped
e186b655d6
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
h-dv/code-index!478
No description provided.