From f249a220913f4421c58c9c6251e4f3dce67e251c Mon Sep 17 00:00:00 2001 From: Klaus Aehlig Date: Mon, 5 May 2025 16:41:37 +0200 Subject: generic rule: fix conflict check For a generic rule, it is an error if map union of various inputs (overlayed in correct order) does not form a proper stage. To implement this check properly, we first have to construct the map of all inputs and only then perform the staging check and not do the check with only the runfiles, as 5e104a526cf76fe75312d2fd288a3c88f506fb0a accidentally did. Fix this. --- CHANGELOG.md | 2 ++ 1 file changed, 2 insertions(+) (limited to 'CHANGELOG.md') diff --git a/CHANGELOG.md b/CHANGELOG.md index 6dc36275..87567ff5 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -24,6 +24,8 @@ A feature release on top of `1.5.0`, backwards compatible. and through its local CAS; this fixes a performance issue. - `just-mr` now also consideres computed roots (as no-op) when reporting progress. +- The "generic" rule now properly detects staging conflicts, taking + the full inputs into account (and not only the runfiles). ## Release `1.5.0` (2025-03-06) -- cgit v1.2.3