Repository navigation
Tags
Tags
chore: prepare 2.1 release (bazel-contrib#3829) Update changelog and version markers --------- Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
ci: update RBE toolchain version from ubuntu2204 to ubuntu2404 (bazel… …-contrib#3778) RBE has dropped support for older platform Fixing https://buildkite.com/bazel/rules-python-python/builds/15434#019e2c2c-c708-4c20-bc05-a9a5b1215d2f (cherry picked from commit 32527de)
ci: soft fail for upcoming bazel job (bazel-contrib#3651) Upcoming RC builds may have regressions, so instead of blocking our CI on their failures, mark them as soft-fail. This way we can be aware of upcoming problems, but not block regular development. (cherry picked from commit 6c05d2d)
test: finish fixing the mocks in the pypi_cache Work towards bazel-contrib#3759
fix(pypi): don't resolve python interpreter when not necessary (bazel… …-contrib#3727) Before the PR we would not set the environment for python interpreter if we would not need the interpreter, but we still resolve the python interpreter, which works on some systems that have a minimal Python installation. With this change we stop resolving the Python interpreter in cases were we should not need it. To ensure that we are not accidentally using it, `python_interpreter` is set to None when we use `pipstar` and do not do any patching, that still requires the Python interpreter. Fixes bazel-contrib#3712 --------- Co-authored-by: Ignas Anikevicius <240938+aignas@users.noreply.github.com> (cherry picked from commit ccdfc8a)
fix(pypi): don't resolve python interpreter when not necessary (bazel… …-contrib#3727) Before the PR we would not set the environment for python interpreter if we would not need the interpreter, but we still resolve the python interpreter, which works on some systems that have a minimal Python installation. With this change we stop resolving the Python interpreter in cases were we should not need it. To ensure that we are not accidentally using it, `python_interpreter` is set to None when we use `pipstar` and do not do any patching, that still requires the Python interpreter. Fixes bazel-contrib#3712 --------- Co-authored-by: Ignas Anikevicius <240938+aignas@users.noreply.github.com> (cherry picked from commit ccdfc8a)
fix(pypi): build the environment on the fly (bazel-contrib#3720) At some point when we started using pipstar, we silently started building the python environment with system python interpreter. This is fine because the environment in those code paths would be unused, but this would break if python was not present on the machine. This PR fixes this by creating the environment on the fly with a little bit of code duplication. Fixes bazel-contrib#3712 --------- Co-authored-by: Richard Levasseur <richardlev@gmail.com> (cherry picked from commit 19a2c04)
sphinxdocs: remove local rules_python dev overrides (bazel-contrib#3705) In the BCR integration test, the local override breaks on BCR itself because a local copy of rules_python isn't part of the test environment. Remove it from the sphinxdocs module, too, because it shouldn't be necessary. The two aren't that closely coupled. (cherry picked from commit c33ba23)
chore: have no-matching-distribution error message hint about target_… …platforms vs requirements_by_platform (bazel-contrib#3701) Based on the slack discussion where a cross-build was failing because `requirements_by_platform` was set, but `target_platforms` wasn't set, have the error message hint at the distinction to better point users for how to fix it. --------- Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com> Co-authored-by: Ignas Anikevicius <240938+aignas@users.noreply.github.com> (cherry picked from commit 6e72de2)
PreviousNext