From f66db4bb21efeead140a453f91280bb9471f24a9 Mon Sep 17 00:00:00 2001 From: Klaus Aehlig Date: Fri, 17 Nov 2023 13:01:28 +0100 Subject: built-in "install" rule: verify well-formedness of resulting stage The install target, like any other target, has to have artifacts and runfiles being proper stages, i.e., in such a way that the keys can be interpreted as names in the file system without causing conflicts. This property used to be unchecked, thus allowing users to define mal-formed targets that, when used as inputs to actions, would result in unspecified layout of the action directory. Fix this by adding an appropriate check enforcing well-formedness of the resulting stage. --- CHANGELOG.md | 2 ++ 1 file changed, 2 insertions(+) (limited to 'CHANGELOG.md') diff --git a/CHANGELOG.md b/CHANGELOG.md index 4af89f8c..6c494b28 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -46,6 +46,8 @@ A feature release on top of `1.2.0`, backwards compatible. - Various minor improvements and typo fixes in the documentation. - Fixed a race condition in an internal cache of `just execute` used for keeping track of running operations. +- The built-in rule `"install"` now properly enforces that the + resulting stage is well-formed, i.e., without tree conflicts. ## Release `1.2.0` (2023-08-25) -- cgit v1.2.3