viiccwen opened a new pull request, #1461:
URL: https://github.com/apache/mahout/pull/1461

   ### Related Issues
   
   Closes #1460 
   
   Supersedes #1444, #1445, #1446, #1452, and #1453.
   
   ### Changes
   
   - [x] Raise the root development PyTorch upper bound to 2.13.0.
   - [x] Raise the QDP development and benchmark PyTorch upper bounds to 2.13.0.
   - [x] Refresh the root and QDP uv lockfiles with all compatible dependency 
updates.
   - [x] Include the pending Pillow 12.3.0, pyasn1 0.6.4, setuptools 83.0.0, 
and PyTorch 2.13.0 updates.
   - [x] Preserve the intentional NumPy, Cirq, and Qiskit Aer upper bounds.
   - [x] Update `ty` suppression comments for the refreshed diagnostic names.
   
   ### Why
   
   The open Python dependency PRs modify overlapping lockfiles. Consolidating 
them avoids repeated lockfile churn and ensures the root and QDP environments 
are updated and validated together.
   
   ### How
   
   Both projects were regenerated with `uv lock --upgrade` after updating only 
the explicit PyTorch caps. No tests or CI workflows were added.
   
   The refreshed `ty` release renamed or tightened several attribute 
diagnostics, so the existing targeted suppressions were updated without 
changing runtime behavior.
   
   ## Checklist
   
   - [x] `uv lock --check`
   - [x] `uv lock --project qdp/qdp-python --check`
   - [x] `uv sync --frozen --group dev`
   - [x] `uv sync --project qdp/qdp-python --frozen --group dev`
   - [x] Python 3.10, 3.11, and 3.12: build the QDP native extension and run 
the full root test suite (`721 passed, 156 skipped` on each version)
   - [x] Python 3.10, 3.11, and 3.12: build from the QDP lockfile and run 
`qdp/qdp-python/tests` (`7 passed, 22 skipped` on each version)
   - [x] `uv run ruff check .`
   - [x] `uv run ty check .`
   - [x] Pre-commit hooks for all changed source and dependency files
   - [x] No new tests or CI workflows added
   


-- 
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