Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: improve the CHANGELOG for the new release #2385

Merged
merged 1 commit into from
Nov 8, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 7 additions & 5 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -62,10 +62,10 @@ A brief description of the categories of changes:
and now `pyyaml` and `PyYAML` will both work.
* (bzlmod) `pip.parse` spoke repository naming will be changed in an upcoming
release in places where the users specify different package versions per
platform in the same hub repository. The naming of the spoke repos is considered
an implementation detail and we advise the users to use the `hub` repository
directly to avoid such breakage in the future. If `rules_python` is missing
features to allow one to do that, please raise tickets.
platform in the same hub repository. The naming of the spoke repos is
considered an implementation detail and we advise the users to use the `hub`
repository directly and make use of {bzl:obj}`pip.parse.extra_hub_aliases`
feature added in this release.

{#v0-38-0-fixed}
### Fixed
Expand All @@ -77,7 +77,9 @@ A brief description of the categories of changes:
which fixes usage of the said wheels using standard package managers.
* (bzlmod) The extension evaluation has been adjusted to always generate the
same lock file irrespective if `experimental_index_url` is set by any module
or not. Fixes
or not. To opt into this behavior, set
{bzl:obj}`pip.parse.parse_all_requirements_files`, which will become the
default in future releases leading up to `1.0.0`. Fixes
[#2268](https://github.com/bazelbuild/rules_python/issues/2268). A known
issue is that it may break `bazel query` and in these use cases it is
advisable to use `cquery` or switch to `download_only = True`
Expand Down