Answer A-476a: a commit still moves its moved modules' code dependents in any repository

This commit is contained in:
2026-11-17 20:21:30 +01:00
parent 75857d9eb7
commit 0ca76cf54f
@@ -1874,3 +1874,9 @@ the principle that settles it, cited as "design 47 G A-n".
revision names: ADR 0633 §1's hold and its hand take-in end (withdraws A-475 and A-475a, which tuned that hold's
validation). (c) A commit moves only modules registered for its own repository; no other repository's module is
recomputed by it. A toolchain or build-module change still moves the modules it builds, at the next take-in.
- **A-476a** (A-476 (c), with the operator's step 4 of the same walkthrough: "the pipeline should cover the entire
delivery group. So if module A is changed and module B depends on code (so a package dependency)"; principle 2) A
commit moves the modules registered for its own repository whose fingerprint changed, and every module, in any
repository, that imports a package of one of those: its code dependents (ADR 0593 §3 stands). What A-476 (c) ends is
only that a commit recomputes modules of another repository that import nothing of what it moved. (From the
develop of A-476: as first written, a mesh-sdk commit no longer moved its importers in other repositories.)