ammachado commented on code in PR #25598:
URL: https://github.com/apache/camel/pull/25598#discussion_r4010810221


##########
.github/workflows/pr-ci-scripts-validation.yml:
##########
@@ -45,3 +46,15 @@ jobs:
         run: |
           cd .github/actions/check-container-upgrade
           python3 -m unittest discover --verbose
+
+      # collect-flakes.py declares defusedxml inline (PEP 723); uv resolves it.
+      - name: Install uv
+      - name: Install uv
+        uses: astral-sh/setup-uv@20cfd1bf945f4377ade1205e4dbc17946fc9a30d # 
v10.0.1
+        with:
+          enable-cache: true
+          version: "0.12.5"
+          python-version: "3.11"
+        run: |
+          cd .github/actions/incremental-build
+          uv run --with defusedxml python3 -m unittest discover --verbose

Review Comment:
   Thanks, confirmed. The earlier suggestion was committed through the GitHub 
UI against a narrower line range than its suggestion block covered, which left 
the duplicate empty step and folded `run:` into the `uses:` step. The 
validation run on `f03024aa` failed for exactly that reason.
   
   Fixed in 6a89cfc0ea0ef9bed1ddcc15f0c80d0be304784c: `Install uv` keeps 
`version: "0.12.5"` / `python-version: "3.11"`, and the test step is split back 
out under its original name (`Test the incremental build scripts`) to keep the 
change limited to what the review asked for. Net diff against `cbda9e9` is only 
the two pin lines.
   
   Validation run is green: 
https://github.com/apache/camel/actions/runs/34912926373. The log shows 
`Successfully installed uv version 0.12.5` and `cpython-3.11.16`, so the pins 
take effect on the runner.
   
   _Claude Code on behalf of Adriano Machado (@ammachado)_
   
   _This was generated by an AI agent and may contain inaccuracies. Please 
verify before relying on it._
   



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to