Repository navigation
[Bot] Update dependencies - #2939
Conversation
57d6556 to
7a1ef98
Compare
|
@timfel, there's a new issue with GraalPy when using the latest version of filelock. Can you check whether it should be fixed in GraalPy or filelock (or both) ? |
a8e46fd to
4c1345c
Compare
ah, it's the |
The dependency update regenerated the constraints and dropped the pip hold-back for GraalPy on Windows, where newer pip breaks. Restore the marker-based pin. Assisted-by: ClaudeCode:claude-opus-4.8
update_constraints now re-applies the GraalPy Windows pip hold-back after uv pip compile, so the bot no longer wipes it each run. Target only the Python versions that ship a GraalPy config (3.12), derived from build-platforms.toml; drop the stale pin from the 3.11 constraints. Assisted-by: ClaudeCode:claude-opus-4.8
PyPy switched its macOS downloads from .tar.bz2 to .tar.gz, which tripped the hard-coded extension assert in install_pypy. Accept both. Assisted-by: ClaudeCode:claude-opus-4.8
filelock >=3.30 imports errno.ENOTSUP, which GraalPy lacks, so virtualenv fails on GraalPy. Hold it at 3.29.4 for GraalPy until the upstream fix ships (~2026-08), reusing the update_constraints workaround mechanism. Assisted-by: ClaudeCode:claude-opus-4.8
|
Android seems to be reliably failing, @mhsmith. |
|
See #2933 (comment): the Android Python 3.15 update should be deferred until the corresponding 3.14 and 3.13 updates next month. |
|
Oh, I forgot about that, thanks! |
Update the versions of our dependencies.
PR generated by "Update dependencies" workflow.