fix(repo-policy-sync): preserve aspect_rules_py dependency - #40
Merged
AlexanderLanin merged 1 commit intoSep 14, 2026
Merged
Conversation
AlexanderLanin
requested review from
MaximilianSoerenPollak,
dcalavrezo-qorix and
nradakovic
as code owners
September 14, 2026 10:53
MaximilianSoerenPollak
approved these changes
Sep 14, 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
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.
Why
The dev-dependency alignment policy currently marks
aspect_rules_pyas a development-only dependency. That changes its dependency visibility and breaks use of Python scripts from outside the development dependency context.aspect_rules_pymust remain unchanged.Example: eclipse-score/docs-as-code#818
What changed
aspect_rules_pyfrom the policy applicability and enforcement configuration.dev_dependency = False.