Bump the all-pip-updates group across 3 directories with 37 updates

requirements/base.txt

@@ -5,20 +5,20 @@ aiohttp>=3.13.5,<3.14.0; python_version < '3.10'
 aiohttp>=3.14.1; python_version >= '3.10'
 apache-libcloud>=3.8.0,<3.9.1; python_version < '3.10'
 apache-libcloud>=3.9.1; python_version >= '3.10'
-certifi>=2026.5.20
-cffi>=2.0.0
+certifi>=2026.6.17
+cffi>=2.1.0
 # cheroot 8.5.2 fails to build with modern setuptools due to setuptools_scm_git_archive dependency
 cheroot>=11.1.2
 cherrypy>=18.10.0
 # We need contextvars for salt-ssh
 contextvars; python_version < '3.7'
-croniter!=0.3.22,>=6.2.2; sys_platform != 'win32'
+croniter!=0.3.22,>=6.2.4; sys_platform != 'win32'
 # cryptography 48.0.0 drops support for Python 3.9.0 and 3.9.1
 # (only >3.9.1 is accepted), but the py3.9 lock files are compiled
 # with --python-version=3.9 which includes those releases. Cap at the
 # last 46.x release for Python 3.9 so uv pip compile can still resolve.
 cryptography>=46.0.7,<48.0.0; python_version < '3.10'
-cryptography>=48.0.0; python_version >= '3.10'
+cryptography>=49.0.0; python_version >= '3.10'
 distro>=1.9.0
 frozenlist>=1.8.0; python_version < '3.11'
 frozenlist>=1.5.0; python_version >= '3.11'
@@ -32,9 +32,9 @@ importlib-metadata>=8.7.0; python_version >= '3.10'
 # jaraco.functools 4.5.0 and jaraco.context 6.1.2 drop Python 3.9; keep the
 # last 3.9-compatible releases there and let py>=3.10 float forward.
 jaraco.functools>=4.4.0,<4.5.0; python_version < '3.10'
-jaraco.functools>=4.4.0; python_version >= '3.10'
+jaraco.functools>=4.5.0; python_version >= '3.10'
 jaraco.context>=6.1.1,<6.1.2; python_version < '3.10'
-jaraco.context>=6.1.1; python_version >= '3.10'
+jaraco.context>=6.1.2; python_version >= '3.10'
 jaraco.text>=4.2.0
 Jinja2>=3.1.6
 jmespath>=1.1.0
@@ -45,32 +45,32 @@ more-itertools>=10.8.0,<11.0.0; python_version < '3.10'
 more-itertools>=11.1.0; python_version >= '3.10'
 # msgpack 1.2.1 drops Python 3.9; keep the last 3.9-compatible release there.
 msgpack>=1.1.2,<1.2.1 ; python_version < '3.10'
-msgpack>=1.1.2 ; python_version >= '3.10' and python_version < '3.13'
+msgpack>=1.2.1 ; python_version >= '3.10' and python_version < '3.13'
 msgpack>=1.1.0 ; python_version >= '3.13'
 # multidict 6.0.4 fails to source-build under clang 17+ with strict int/pointer
 # conversion checks (macOS 15 onedir builds compile from sdist via
 # --no-binary=:all:). 6.6+ fixed the C source compatibility.
-multidict>=6.6.0
+multidict>=6.7.1
 # opentelemetry 1.43.0 (and exporter-prometheus 0.64b0) drop Python 3.9; keep
 # the last 3.9-compatible releases there and let py>=3.10 float forward.
 opentelemetry-api>=1.41.1,<1.43.0; python_version < '3.10'
-opentelemetry-api>=1.41.1; python_version >= '3.10'
+opentelemetry-api>=1.43.0; python_version >= '3.10'
 opentelemetry-sdk>=1.41.1,<1.43.0; python_version < '3.10'
-opentelemetry-sdk>=1.41.1; python_version >= '3.10'
+opentelemetry-sdk>=1.43.0; python_version >= '3.10'
 opentelemetry-exporter-otlp-proto-http>=1.41.1,<1.43.0; python_version < '3.10'
-opentelemetry-exporter-otlp-proto-http>=1.41.1; python_version >= '3.10'
+opentelemetry-exporter-otlp-proto-http>=1.43.0; python_version >= '3.10'
 opentelemetry-exporter-prometheus>=0.62b1,<0.64b0; python_version < '3.10'
-opentelemetry-exporter-prometheus>=0.62b1; python_version >= '3.10'
+opentelemetry-exporter-prometheus>=0.64b0; python_version >= '3.10'
 # xxhash 3.8.0 drops Python 3.9; keep the last 3.9-compatible release there.
 xxhash>=3.7.0,<3.8.0; python_version < '3.10'
-xxhash>=3.7.0; python_version >= '3.10'
+xxhash>=3.8.1; python_version >= '3.10'
 # Packaging 24.1 imports annotations from __future__ which breaks salt ssh
 # tests on target hosts with older python versions.
 packaging>=26.2; python_version < '3.11'
 packaging==24.0; python_version >= '3.11'
 psutil<6.0.0; python_version <= '3.9'
-psutil>=5.0.0; python_version >= '3.10'
-pyasn1>=0.6.3
+psutil>=7.2.2; python_version >= '3.10'
+pyasn1>=0.6.4
 pycparser>=2.23,<3.0; python_version < '3.10'
 pycparser>=3.0; python_version >= '3.10'
 # pymssql 2.3.12+ dropped win32 (32-bit Windows) wheels; 3008.x still
@@ -81,7 +81,7 @@ pymssql==2.3.11; sys_platform == 'win32' and python_version >= '3.11'
 # pyopenssl 26.3.0 requires cryptography>=49 which drops Python 3.9; keep the
 # last 3.9-compatible release there and let py>=3.10 float forward.
 pyopenssl>=26.2.0,<26.3.0; python_version < '3.10'
-pyopenssl>=26.2.0; python_version >= '3.10'
+pyopenssl>=26.3.0; python_version >= '3.10'
 python-dateutil>=2.9.0.post0
 python-gnupg>=0.5.6
 pythonnet>=3.0.1; sys_platform == 'win32' and python_version < '3.11'
@@ -91,14 +91,14 @@ pywin32>=312; sys_platform == 'win32'
 pycryptodomex>=3.23.0
 PyYAML>=6.0.3
 requests>=2.32.5; python_version < '3.10'
-requests<2.32.0 ; python_version >= '3.10' and python_version < '3.11'
+requests<2.35.0 ; python_version >= '3.10' and python_version < '3.11'
 requests>=2.32.5 ; python_version >= '3.11'
 rpm-vercmp; sys_platform == 'linux'
 setproctitle>=1.3.7
 timelib>=0.3.0; python_version < '3.11'
 timelib>=0.3.0; python_version >= '3.11'
-tornado>=6.5.6
-truststore>=0.10.0; python_version >= "3.10"
+tornado>=6.5.7
+truststore>=0.10.4; python_version >= "3.10"
 # Python 3.9 stays on urllib3 1.26.x because botocore on py3.9 hard
 # requires urllib3 < 2 and Salt 3008.x still ships py3.9 lockfiles.
 # The Python 3.10+ floor carries the urllib3 2.6.3 CVE backports
@@ -107,14 +107,14 @@ urllib3>=1.26.20,<2.0.0; python_version < '3.10'
 urllib3>=2.7.0; python_version >= '3.10'
 # virtualenv 21.5.1 drops Python 3.9; keep the last 3.9-compatible release there.
 virtualenv>=21.4.2,<21.5.1; python_version < '3.10'
-virtualenv>=21.4.2; python_version >= '3.10'
+virtualenv>=21.6.1; python_version >= '3.10'
 # Transitive of virtualenv; some uv resolver caches pin a stale 3.25
 # version that conflicts with the CI floor of 3.29.1 on Python 3.10+.
-filelock>=3.29.1; python_version >= '3.10'
+filelock>=3.29.7; python_version >= '3.10'
 filelock>=3.19.1,<3.29.0; python_version < '3.10'
 vultr>=1.0.1
 wmi>=1.5.1; sys_platform == 'win32'
 xmltodict>=1.0.4; sys_platform == 'win32'
 # zipp 4.1.0 drops Python 3.9; keep the last 3.9-compatible release there.
 zipp>=3.23.1,<4.1.0; python_version < '3.10'
-zipp>=3.23.1; python_version >= '3.10'
+zipp>=4.1.0; python_version >= '3.10'

requirements/build.txt

@@ -1,2 +1,2 @@
 twine
-build>=1.4.4
+build>=1.5.1

requirements/constraints.txt

@@ -10,22 +10,22 @@ wheel >= 0.47.0
 # bootstraps build envs with), e.g. yarl on Python 3.14 where no cp314
 # wheel is available under salt's ``--no-binary=:all:`` policy.
 setuptools >= 78.1.1
-# Cap setuptools-scm < 10 in PEP 517 build envs. 10.1.1 (2026-06-22) split
+# Cap setuptools-scm < 11 in PEP 517 build envs. 10.1.1 (2026-06-22) split
 # version inference out into the ``vcs-versioning`` package; that path raises
 # ``LookupError: setuptools-scm was unable to detect version`` for source
 # tarballs that ship a ``PKG-INFO`` but no ``.git`` (e.g. cheroot 11.1.2 on
 # PyPI), breaking ``--no-binary=:all:`` onedir builds. PIP_CONSTRAINT
 # propagates to PEP 517 build envs since pip 22.1, so capping here keeps
 # build envs on the pre-split 9.x series for every source build.
-setuptools-scm < 10
+setuptools-scm < 11
 # pip 25.2 is the version that relenv's onedir ships with, and that
 # tools/pkg/build.py downloads + patches in pkg/patches/pip-urllib3/.
 # Bumping past 25.2 here causes the noxfile bootstrap pip install in
 # the lint-pre-commit hook to upgrade the just-installed 25.2 inside
 # the pre-commit hook venv on Python 3.14, which leaves the venv in a
 # corrupted state because pip 26.0.1's vendored pygments wheel is
 # missing the modeline submodule on cpython 3.14. Stay on 25.2.
-pip == 25.2
+pip == 26.1.2
 markdown-it-py < 3.0.0; python_version == "3.9"
 # myst-docutils 4.x (the latest supporting Python 3.10) requires
 # markdown-it-py ~=3.0; the 5.x line that pairs with markdown-it-py 4.x

requirements/pytest.txt

@@ -1,8 +1,8 @@
 mock >= 5.2.0
 # PyTest
-docker >= 7.1.0; python_version >= '3.8'
+docker >= 7.2.0; python_version >= '3.8'
 docker < 7.1.0; python_version < '3.8'
-pytest >= 8.4.2, <9
+pytest >= 9.1.1, < 10
 pytest-salt-factories >= 1.0.5
 pytest-helpers-namespace >= 2021.12.29
 pytest-subtests

requirements/static/ci/common.txt

@@ -14,21 +14,21 @@ bcrypt
 # our urllib3 floor is 2.6.3 so we skip the boto3 cloud module tests on
 # 3.9 by not pinning it here. The bare `boto3` package is still
 # available transitively for any tool that needs it.
-boto3>=1.43.24; python_version >= '3.10'
+boto3>=1.43.46; python_version >= '3.10'
 boto>=2.49.0
 # botocore 1.43.24 requires Python>=3.10. The only versions available on
 # 3.9 (botocore<1.43) hard-pin urllib3<1.27, which conflicts with our
 # urllib3>=2.6.3 floor. Drop botocore on 3.9 like boto3.
-botocore>=1.43.24; python_version >= '3.10'
+botocore>=1.43.46; python_version >= '3.10'
 cryptography>=46.0.7,<48.0.0; python_version < '3.10'
-cryptography>=48.0.0; python_version >= '3.10'
-cffi>=2.0.0
+cryptography>=49.0.0; python_version >= '3.10'
+cffi>=2.1.0
 cherrypy>=18.10.0
 clustershell
 dnspython
 etcd3-py==0.1.6
 filelock>=3.19.1 ; python_version < '3.10'
-filelock>=3.29.1 ; python_version >= '3.10'
+filelock>=3.29.7 ; python_version >= '3.10'
 gitpython>=3.1.50
 google-auth==2.35.0; python_version == '3.9'
 jmespath>=1.1.0
@@ -55,7 +55,7 @@ napalm; sys_platform != 'win32' and python_version < '3.10'
 paramiko>=5.0.0; sys_platform != 'win32' and sys_platform != 'darwin'
 passlib>=1.7.4
 pycryptodomex
-pynacl>=1.5.0
+pynacl>=1.6.2
 pyinotify>=0.9.6; sys_platform != 'win32' and sys_platform != 'darwin' and platform_system != "openbsd"
 python-etcd>=0.4.5
 pyvmomi
@@ -67,15 +67,15 @@ textfsm
 toml
 # vcert 0.18.x adds hard pins on cryptography, pynacl, and six that
 # conflict with every other CI requirement; stay on 0.9.x.
-vcert~=0.9.0; sys_platform != 'win32'
+vcert~=0.9.1; sys_platform != 'win32'
 virtualenv>=21.4.2,<21.5.1; python_version < '3.10'
-virtualenv>=21.4.2; python_version >= '3.10'
+virtualenv>=21.6.1; python_version >= '3.10'
 watchdog>=6.0.0
 websocket-client>=1.9.0
 # werkzeug is a dependency of moto
 werkzeug>=3.1.8
 xmldiff>=2.7.0,<3.0; python_version < '3.10'
-xmldiff>=2.7.0; python_version >= '3.10'
+xmldiff>=3.0; python_version >= '3.10'
 # Available template libraries that can be used
 genshi>=0.7.11
 cheetah3>=3.2.6.post1

requirements/static/ci/darwin.txt

@@ -1,7 +1,7 @@
 pygit2>=1.13.1,<1.18.0; python_version < '3.11'
-pygit2>=1.19.2; python_version >= '3.11'
+pygit2>=1.19.3; python_version >= '3.11'
 yamllint
-mercurial>=7.2.2
+mercurial>=7.2.3
 hglib
 # Pin versions to match 3007.x
 apache-libcloud>=3.8.0,<3.9.1; python_version < '3.10'

requirements/static/ci/freebsd.txt

@@ -1,5 +1,5 @@
 # FreeBSD static CI requirements
 
 yamllint
-mercurial>=7.2.2
+mercurial>=7.2.3
 hglib

requirements/static/ci/lint.txt

@@ -1,12 +1,12 @@
 # Lint requirements
 
-docker >= 7.1.0; python_version >= '3.8'
+docker >= 7.2.0; python_version >= '3.8'
 docker < 7.1.0; python_version < '3.8'
 # pylint 4 introduces new default-on E0606/E0601/E0602 checks
 # (possibly-used-before-assignment / used-before-assignment) that the
 # Salt 3008.x codebase has not been audited for; bumping to 4.x turns
 # pre-existing warnings into hard CI failures across salt/, tools/,
 # and tests/. Cap to ~=3.1.0 until the codebase is audited.
-pylint~=3.1.0
+pylint~=3.3.9
 SaltPyLint>=2024.2.5
 toml

requirements/static/ci/linux.txt

@@ -1,7 +1,7 @@
 # Linux static CI requirements
 pyiface
 pygit2>=1.13.1,<1.18.0; python_version < '3.11'
-pygit2>=1.19.2; python_version >= '3.11'
+pygit2>=1.19.3; python_version >= '3.11'
 pymysql>=1.2.0
 # ansible release lines support different Python versions:
 #   ansible-core / ansible 10.x — Python 3.10+ (controller and managed)
@@ -17,12 +17,12 @@ pymysql>=1.2.0
 # Python 3.10+ as a controller and installs cleanly on the py3.11 onedir.
 # See PR #69527 / issue #69526.
 ansible>=10.7.0,<11.0.0; python_version >= '3.10' and python_version < '3.12'
-ansible>=14.0.0; python_version >= '3.12'
+ansible>=14.1.0; python_version >= '3.12'
 twilio>=9.10.9
 python-telegram-bot>=20.3,<22.0; python_version < '3.10'
-python-telegram-bot>=22.7; python_version >= '3.10'
+python-telegram-bot>=22.8; python_version >= '3.10'
 yamllint
-mercurial>=7.2.2
+mercurial>=7.2.3
 hglib
 redis
 python-consul