Skip to content

Tags

Tags

2.5.0

Toggle 2.5.0's commit message
fix(pypi): respect uv.lock dependency platform markers (bazel-contrib…

…#4286)

Fixes bazel-contrib#4287.

`pip.parse` can select Linux-only dependencies on macOS because it
ignores platform conditions on dependency edges in `uv.lock`. For
example, `uvloop; sys_platform == 'linux'` incorrectly selects a source
archive on macOS.

This change follows dependencies from the workspace roots and keeps each
package only on the platforms where it is reachable. It preserves
support for optional extras and development dependency groups.

Validation:
- All 94 parser and uv-lock tests pass, including regression coverage
for platform filtering, extras, and development groups.
- The real uvloop reproduction now selects only the Linux wheel.
- Buildifier and `git diff --check` pass.

Includes updated API documentation and a release note.

---------

Co-authored-by: Richard Levasseur <richardlev@gmail.com>
(cherry picked from commit 8a3b77c)

Work towards bazel-contrib#4388

2.5.0-rc4

Toggle 2.5.0-rc4's commit message
fix(pypi): respect uv.lock dependency platform markers (bazel-contrib…

…#4286)

Fixes bazel-contrib#4287.

`pip.parse` can select Linux-only dependencies on macOS because it
ignores platform conditions on dependency edges in `uv.lock`. For
example, `uvloop; sys_platform == 'linux'` incorrectly selects a source
archive on macOS.

This change follows dependencies from the workspace roots and keeps each
package only on the platforms where it is reachable. It preserves
support for optional extras and development dependency groups.

Validation:
- All 94 parser and uv-lock tests pass, including regression coverage
for platform filtering, extras, and development groups.
- The real uvloop reproduction now selects only the Linux wheel.
- Buildifier and `git diff --check` pass.

Includes updated API documentation and a release note.

---------

Co-authored-by: Richard Levasseur <richardlev@gmail.com>
(cherry picked from commit 8a3b77c)

Work towards bazel-contrib#4388

2.5.0-rc3

Toggle 2.5.0-rc3's commit message
fix: stop rules_python from warning about its own implicit __init__.p…

…y creation (bazel-contrib#4451)

When rules_python is used as a Bzlmod dependency without
--incompatible_default_to_explicit_init_py (which is deprecated in
Bazel 10), rules_python emits implicit __init__.py deprecation
warnings for its own internal targets (//tools:wheelmaker,
//python/private:py_wheel_dist,
//python/private:py_console_script_gen_py, and
//tools/publish:twine).

Enable rules_python_config.explicit_init_py(default = True) in
MODULE.bazel so all targets in rules_python default to explicit
__init__.py behavior.

Closes bazel-contrib#4448

(cherry picked from commit ab7da31)

Work towards bazel-contrib#4388

2.5.0-rc2

Toggle 2.5.0-rc2's commit message
fix(coverage): bundle Python 3.15 coverage wheels (bazel-contrib#4401)

Python 3.15 toolchains can run tests, but bazel coverage fails during
analysis when configure_coverage_tool = True. Without cp315 entries, the
coverage dependency table selects a pure Python fallback wheel, causing
the generated BUILD file’s coverage/*.so glob to fail.

Add coverage.py 7.17.0 wheels for Python 3.15 on Linux and macOS,
including free-threaded interpreters. Preserve existing wheels for older
Python versions, since upgrading the entire table would drop Python 3.9
and 3.10 support.

Update the dependency generator to include cp315 and recognize the macOS
10.15 x86_64 wheel tag.

(cherry picked from commit 3f3e7ea)

Work towards bazel-contrib#4388

2.5.0-rc1

Toggle 2.5.0-rc1's commit message
fix(coverage): bundle Python 3.15 coverage wheels (bazel-contrib#4401)

Python 3.15 toolchains can run tests, but bazel coverage fails during
analysis when configure_coverage_tool = True. Without cp315 entries, the
coverage dependency table selects a pure Python fallback wheel, causing
the generated BUILD file’s coverage/*.so glob to fail.

Add coverage.py 7.17.0 wheels for Python 3.15 on Linux and macOS,
including free-threaded interpreters. Preserve existing wheels for older
Python versions, since upgrading the entire table would drop Python 3.9
and 3.10 support.

Update the dependency generator to include cp315 and recognize the macOS
10.15 x86_64 wheel tag.

(cherry picked from commit 3f3e7ea)

Work towards bazel-contrib#4388

2.5.0-rc0

Toggle 2.5.0-rc0's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
Prepare release v2.5.0 (bazel-contrib#4389)

Work towards bazel-contrib#4388

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

2.4.6

Toggle 2.4.6's commit message
feat(toolchains): update Python toolchains to latest patch releases (b…

…azel-contrib#4369)

Recent Python patch releases address compromised eMudhra intermediate
CA keys in the bundled CA bundle and provide the Python 3.15 GA and
patch releases. Without these updates, default toolchains use older
patch releases and pre-release 3.15 builds.

Add the `20261009` and `20261026` `python-build-standalone` runtime
releases, remove pre-release `3.15.0` entries, and update default
minor version mappings to `3.10.22`, `3.11.18`, `3.12.16`, `3.13.18`,
`3.14.10`, and `3.15.2`.

Fixes bazel-contrib#4358

(cherry picked from commit 6f58700)

Work towards bazel-contrib#4373

2.4.5

Toggle 2.4.5's commit message
fix(uv): upgrade default uv to 0.13.5 (bazel-contrib#4329)

uv versions prior to 0.13.4 bundle the compromised emSign ECC Root CA -
G3 root certificate in webpki-root-certs (GHSA-hq85-5cpj-mr62).

Upgrade the default uv version and configured versions in examples and
integration tests to 0.13.5, which removes the compromised root
certificate and rejects certificate chains containing compromised
eMudhra intermediate keys.

Work towards bazel-contrib#4299

(cherry picked from commit ea8ffe8)

Work towards bazel-contrib#4332

2.4.4

Toggle 2.4.4's commit message
fix(pypi): upgrade pip to 26.2.2 and pip-tools to 7.6.2 (bazel-contri…

…b#4310)

`pip` versions prior to 26.2.2 bundle an older `certifi` release that
still trusts the distrusted eMudhra (`emSign ECC Root CA - G3`) root
certificate when `pip` makes network requests during requirements
locking, sdist builds, or wheel fallback downloads.

Upgrade the internal `pip` dependency to 26.2.2 so `pip` uses the
updated `certifi` bundle, and upgrade `pip-tools` to 7.6.2 for
compatibility with `pip` 26.2.2.

Work towards bazel-contrib#4299

(cherry picked from commit f6d70c6)

Work towards bazel-contrib#4321

2.4.3

Toggle 2.4.3's commit message
build(deps): bump the uv group across 10 directories with 1 update (b…

…azel-contrib#4297)

Update certifi to 2026.10.19 across lockfiles, test constraints, and
vendored requirements to address the eMudhra/emSign CA certificate
security advisory (bazel-contrib#4299), and refresh the Gazelle manifest integrity
hash and CHANGELOG.md for 2.4.3.

(cherry picked from commit 711b314)

Work towards bazel-contrib#4301