Repository navigation
Tags
Tags
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
fix(zipapp): store _solib shared libraries as files, not absolute sym… …links (bazel-contrib#4211) Since bazel-contrib#4165, the zipper keeps a symlink for an input whose original source is a symlink, looking through the absolute symlink the Bazel sandbox exposes the input as. For the `_solib` entries Bazel creates for shared libraries, the original source is itself an absolute symlink into the build machine's output base, so the zipapp stored entries like runfiles/_main/_solib_x86_64/libST-..._Slibgrpc.so -> /home/<user>/.cache/bazel/<hash>/execroot/_main/bazel-out/.../libgrpc.so which dangle on any other machine. Any zipapp whose Python code loads a shared library from `_solib` (a C extension that links a `cc_library` dynamically, or `libpython` for an extension that links it) fails to load it outside the machine that built it. Before bazel-contrib#4165 these files were copied. To fix, only keep the looked-through target when it is relative, e.g. `libpython3.10.so -> libpython3.10.so.1.0` inside the runtime, which is what the size optimization in bazel-contrib#4165 is for. Otherwise the file is stored. * Adds a zipper test with the `_solib` shape: a sandbox symlink to an absolute symlink to the library. It fails without the fix ("should NOT be a symlink but is"). (cherry picked from commit 381762a) Work towards bazel-contrib#4232
feat(toolchains): update CPython 3.15.0 from rc2 to rc3 (bazel-contri… …b#4220) Make CPython 3.15.0rc3 available from the 20261003 python-build-standalone release. Replace the 3.15.0rc2 runtime entries in the manifest with 3.15.0rc3 and update the default 3.15 minor version mapping. (cherry picked from commit 87b8ae6) Work towards bazel-contrib#4224
feat(pypi): add py.typed files to pyi_srcs (bazel-contrib#4202) Wheel libraries automatically include all their .pyi files in `pyi_srcs`, but py.typed files are just as important. In this patch we begin including them and make the same change to the runfiles py_library as well. (cherry picked from commit 28fe2e8) Work towards bazel-contrib#4175
feat(pypi): add py.typed files to pyi_srcs (bazel-contrib#4202) Wheel libraries automatically include all their .pyi files in `pyi_srcs`, but py.typed files are just as important. In this patch we begin including them and make the same change to the runfiles py_library as well. (cherry picked from commit 28fe2e8) Work towards bazel-contrib#4175
feat(toolchains): update CPython 3.15.0 from rc1 to rc2 (bazel-contri… …b#4199) Make CPython 3.15.0rc2 available from the 20260929 python-build-standalone release. Replace the 3.15.0rc1 runtime entries in the manifest with 3.15.0rc2 and update the default 3.15 minor version mapping. (cherry picked from commit 1c026a6) Work towards bazel-contrib#4175
fix(zipapp): reduce bundled interpreter size (bazel-contrib#4165) Bazel reports source symlinks as regular files, causing Python executable aliases to be copied into zipapps as full binaries. Hermetic runtimes also include shared libpython artifacts even when the interpreter links Python statically. Preserve source symlinks through sandbox indirection and exclude libpython shared objects from runtime files while retaining them for explicit native dependencies. Add regression coverage for archive structure and native extension loading. Fixes bazel-contrib#3534 Fixes bazel-contrib#4163 --------- Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> Co-authored-by: Richard Levasseur <richardlev@gmail.com> (cherry picked from commit fd22cff) Work towards bazel-contrib#4175
build(release): exclude devguide.md from version marker checks (bazel… …-contrib#4185) `docs/devguide.md` documents how to use `VERSION_NEXT_*` markers, which causes the release workflow version marker check to fail on release branches. Exclude `devguide.md` from the version marker check script and the release tool replacement patterns. Work towards bazel-contrib#4175
docs(changelog): add 2.3.4 entry for win32 Python runtimes PR bazel-contrib#4156 merged the win32 Python runtime additions directly to the release/2.3 branch without a changelog update. Add the 2.3.4 release section to CHANGELOG.md so the upcoming patch release documents the new toolchains. Work towards bazel-contrib#4173
fix(gazelle): fix module map for old-style namespaces (bazel-contrib#… …4135) The performance tweak in bazel-contrib#3415 which parallelized gazelle module map generation calls simplify() on wheels individually, which always results in entries which collapse to the highest level modules which contain __init__.py files. But when two wheels do old-style namespace packages by both including that file under their top-level module, they simplify down to the top-level module, clobber each other when merged, and wind up with one wheel getting mapped for the entire namespace. This causes bug bazel-contrib#3528. We fix this by deferring our call to simplify() until after we've merged all the wheels' module info. Fixes bazel-contrib#3528 (cherry picked from commit a6606a5) Work towards bazel-contrib#4121
PreviousNext