Skip to content

Tags

Tags

2.0.0-rc2

Toggle 2.0.0-rc2's commit message
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)

2.0.0-rc1

Toggle 2.0.0-rc1's commit message
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)

2.0.0-rc0

Toggle 2.0.0-rc0's commit message
chore: populate 2.0 for VERSION_NEXT_FEATURE for py_wheel add_path_pr…

…efix (bazel-contrib#3703)

The add_path_prefix feature is in the 2.0 branch, but its version
marker wasn't populated. Set it to 2.0.0

(cherry picked from commit 9790ae0)

1.9.0

Toggle 1.9.0's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
feat(pypi): make whl_library reproducible under pipstar (bazel-contri…

…b#3589) (bazel-contrib#3632)

This is testing the new API to make use of remote caching mechanisms.

Needs: bazelbuild/bazel#27634

---------

(cherry picked from commit 06aa36d)

Co-authored-by: Ignas Anikevicius <240938+aignas@users.noreply.github.com>

1.9.0-rc1

Toggle 1.9.0-rc1's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
feat(pypi): make whl_library reproducible under pipstar (bazel-contri…

…b#3589) (bazel-contrib#3632)

This is testing the new API to make use of remote caching mechanisms.

Needs: bazelbuild/bazel#27634

---------

(cherry picked from commit 06aa36d)

Co-authored-by: Ignas Anikevicius <240938+aignas@users.noreply.github.com>

1.9.0-rc0

Toggle 1.9.0-rc0's commit message
chore: repleace version marker in features.bzl

(cherry picked from commit 3ddb601)

1.8.5

Toggle 1.8.5's commit message
fix(pypi): normalize extras in requirement strings per PEP 685 (bazel…

…-contrib#3588)

## Summary

Extras parsed from requirement strings (e.g., from `requirements.txt`)
were not being normalized, causing mismatches when evaluating PEP 508
marker expressions. For example, `sqlalchemy[postgresql-psycopg2binary]`
would fail to resolve `psycopg2-binary` as a transitive dependency
because the wheel METADATA marker expression `extra ==
"postgresql_psycopg2binary"` uses the underscore-normalized form (per
PEP 685), while the extras set retained the original hyphenated form
from the requirement string.

## Before

```
# requirements.txt
sqlalchemy[postgresql-psycopg2binary]==2.0.36

# Parsed extras: ["postgresql-psycopg2binary"]
# Marker evaluation: "postgresql-psycopg2binary" != "postgresql_psycopg2binary" -> MISS
# Result: psycopg2-binary NOT included as a dependency
```

## After

```
# requirements.txt
sqlalchemy[postgresql-psycopg2binary]==2.0.36

# Parsed extras: ["postgresql_psycopg2binary"]  (normalized)
# Marker evaluation: "postgresql_psycopg2binary" == "postgresql_psycopg2binary" -> MATCH
# Result: psycopg2-binary correctly included as a dependency
```

## Changes

- **`python/private/pypi/pep508_requirement.bzl`**: Apply
`normalize_name()` to each extra during requirement parsing, consistent
with how the package name is already normalized.
- **`tests/pypi/pep508/requirement_tests.bzl`**: Updated existing test
expectation for case normalization and added test case for hyphenated
extras
(`sqlalchemy[asyncio,postgresql-psycopg2binary,postgresql-asyncpg]`).
- **`tests/pypi/pep508/deps_tests.bzl`**: Added
`test_extras_with_hyphens_are_normalized` integration test confirming
that dependencies gated behind hyphenated extras are correctly resolved.
- **`CHANGELOG.md`**: Added entry under Unreleased > Fixed.

Fixes bazel-contrib#3587

---------

Co-authored-by: Ignas Anikevicius <240938+aignas@users.noreply.github.com>
(cherry picked from commit 9fe42b1)

1.8.4

Toggle 1.8.4's commit message
fix(pipstar): handle a corner case for compatible version evaluation (b…

…azel-contrib#3583)

It seems that there was one corner case that was left unhandled.
In theory we should also handle `3 ~= 3.0.0`, but the fix for that may
be a little more involved and I want to leave it for later. However,
that case is unlikely to occur in reality because `LHS` for our cases
will most likely have 2 components.

Whilst at it prepare for the patch release (bazel-contrib#3584).

Fixes bazel-contrib#3580

(cherry picked from commit a32c744)

1.8.3

Toggle 1.8.3's commit message
fix(pip): simply extract whl contents to the current directory (bazel…

…-contrib#3549)

Before we would try to get the whl path and extract to the sibling
directory. Whilst this is not failing right now, technically this is not
the best behaviour because the whl itself may come from elsewhere. This
PR is simplifying code to see if it helps solve an issue on Windows.

Fixes bazel-contrib#3543

(cherry picked from commit abe2699)

1.8.2

Toggle 1.8.2's commit message
fix: explicitly symlink all .so files, not just ones with lib prefix (b…

…azel-contrib#3538)

Some packages, such as tensorflow, have regular C libraries that don't
use
a `lib*` suffix. The symlink optimization logic wouldn't link these
directly,
which made the dynamic linker unable to find their dependencies.

To fix, explicitly symlink all `.so` files, since we can't determine
which
are Python C modules and regular C libraries.

Fixes bazel-contrib#3529

(cherry picked from commit b4ec825)