Repository navigation
CI: add Python validation job (uv, validate.py, unit tests) - #7
Merged
Merged
Conversation
The existing workflow only ran `mvn -B verify`, so the repo's own gate — `tools/validate.py` plus the validator's unit tests — was never enforced on PRs. Adds a python-validate job that installs uv via pipx (already on the runner image, avoids a new third-party action on the ASF allowlist), syncs dev dependencies, validates examples, and runs the unittest suite. Note: validate.py currently exits 0 vacuously since examples/ is not yet on main; the job starts validating records automatically once examples land. The unit tests provide real signal in the meantime. Apache-ai: Yes Generated-by: Devin (SWE-2 High) Reviewed-by: nkn
Contributor
|
Thank you NKN :) |
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
ci.ymlpreviously ran onlymvn -B verify, so the repo's ownPython-side gate —
tools/validate.pyand the validator's unit tests —was never enforced on PRs.
python-validatejob: installuvviapipx(preinstalled onGitHub-hosted runners; avoids adding a third-party action such as
astral-sh/setup-uvto the ASF allowlist),uv sync --extra dev,tools/validate.py, andpython -m unittest discover -s tests.Notes
tools/validate.pycurrently exits 0 vacuously becauseexamples/isnot yet on
main; the job will begin validating records automaticallyonce examples land. The unit tests provide real signal in the meantime.
runcommands are exactly the documented local gate fromSETUP.md/AGENTS.md; verified locally on Linux.
Apache-ai: Yes
Generated-by: Devin (SWE-2 High)
Reviewed-by: nkn