feat(config): shared-path change semantics via extra_paths and shared_paths - #540
Merged
Merged
Conversation
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
…_paths Per-component versioning scoped commits to a component's own path, so a change to a shared library or root config outside every component path bumped no component and released nothing. Add two additive, optional fields: per-component extra_paths (paths beyond the component's own that both trigger and version it) and top-level shared_paths (fanned into every component). Both are threaded to all three sinks so a shared change is not silently half-handled: the emitted push-paths filter (the workflow fires), the version calculation (GetCommitsForPaths includes the extra paths so a breaking shared commit bumps correctly), and detectChanges (extra paths union into each build and deploy's non-empty triggers, so a shared change does not bump a version whose builds then skip; empty run-always triggers are preserved). shared_paths is rejected per component. When both fields are unset the resolved paths, emitted output, and version calc are unchanged, so single-component output stays byte-identical. Also correct a now-false doc-comment about extra_triggers.merge_group. Signed-off-by: Joshua Temple <joshua.temple@stablekernel.com>
joshua-temple
force-pushed
the
feat/shared-path-change-semantics
branch
from
July 9, 2026 08:17
d393d56 to
3e68dcb
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Per-component versioning scoped commits to a component's own
path, so a change to a shared library or root config (outside every component path) bumped no component and released nothing. A busy monorepo changes shared code constantly, so this was the top product gap.Feature
Two additive, optional fields:
extra_paths: paths beyond the component's own that both trigger and version it;shared_paths: fanned into every component (rejected per-component).Both are threaded to all three sinks so a shared change is never half-handled:
GetCommitsForPathsincludes the extra paths, so afeat!:shared commit bumps correctly.Byte-identical
When both fields are unset, resolved paths, emitted output, and version calc are unchanged; single-component output stays byte-identical (baseline gate green).
Verification
Red-before/green-after unit tests: a shared-path commit bumps the consuming component (and
feat!:bumps major);shared_pathsfans to all; an undeclared shared path bumps nothing;detectChangesunions extra paths; resolve fan-out + byte-identical-when-unset. Fullgo test ./...(2686),-race,golangci-lintclean; three schema copies byte-identical; docs build. e2e scenario 56 asserts the emitted fan-out. Note: the runtime version bump is proven by the orchestrate unit tests here; the live-fleet runtime proof is Stage 3 (a shared-path wave). Also fixes a now-falsemerge_queuedoc-comment.