Skip to content

Conversation

@sil2100
Copy link
Member

@sil2100 sil2100 commented Jan 13, 2026

Depending on unversioned py3 module packages can lead to various hard-to-debug issues. We can and should be more explicit on which python version we are supporting, making sure we pull in the right module version at any time.

Signed-off-by: Łukasz 'sil2100' Zemczak <lukasz.zemczak@chainguard.dev>
@sil2100
Copy link
Member Author

sil2100 commented Jan 13, 2026

I made this SeverityError as I do not know if SeverityWarning provides any feedback to the developer on PRs. Was thinking of an exception mechanism, but this would require a bit more work as we do not seem to save comment fields from the yaml.Node information into the parsed config structures. I don't know if we even need these.

@justinvreeland
Copy link
Member

Looks fine to me. We'll want to audit the packages before making this enforcing or we'll cause breakage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants