fix(gds): declare both gitlink and reusable-workflow consumption - #87
Merged
Conversation
Signed-off-by: rldyourmnd <danil@nddev.it.com>
Signed-off-by: rldyourmnd <danil@nddev.it.com>
This was referenced Sep 7, 2026
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
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.
Summary
Declare both git-submodule and runtime-service consumption in the GDS module anchor. The GDS schema uses runtime-service for a workflow-module-consumer; declaring only git-submodule made typed consumer inventory reject valid reusable-workflow relationships. Closes #86.
Regenerated the bundle lock through GDS plan/apply/verify with the existing verified stable 0.8.0 bundle; no bundle upgrade or consumer rollout. The compiled policy output is unchanged.
Type of change
Threat-model note
No workflow behavior or permission is changed. The declaration describes how the existing product is consumed; it grants no runtime, token or repository access.
Permissions diff
None.
packages: writekeeps the same scope; its explanation is now inline.Verification
scripts/validate_module.sh/validate_all.py --tier core: passed.Existing examples/catalog/workflow behavior remain unchanged. No runtime fixture execution, release publication or downstream pin migration is claimed by this source-only correction.
Tier impact
Both existing public and private consumers can be modeled correctly. No billing or runner-routing change.