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

Make bzlmod repo rules compatible with Bazel 8 #1083

Merged
merged 1 commit into from
Oct 16, 2024

Conversation

yukawa
Copy link
Collaborator

@yukawa yukawa commented Oct 16, 2024

Description

There is an upcoming behavior change in bzlmod --incompatible_use_plus_in_repo_names, which changes the separator character in canonical repo names from tilde ~ to plus + due to I/O performance issue in Windows.

The above flag is planned to be enabled by default in Bazel 8.0, which is expected to be released on November 2024. Let's update our custom repository rules so that they can continue working with Bazel 8.0.

Issue IDs

This is a follow up to

Steps to test new behaviors (if any)

A clear and concise description about how to verify new behaviors (if any).

  • OS: Ubuntu 24.04
  • Steps:
    1. Make sure you are using Bazel 7.3.2.
    2. bazel build --config oss_linux package --config release_build --incompatible_use_plus_in_repo_names
    3. Confirm the build succeeds.

There is an upcoming behavior change in bzlmod

  --incompatible_use_plus_in_repo_names,

which changes the separator character in canonical repo names from
tilde `~` to plus `+` due to I/O performance issue in Windows.

 * bazelbuild/bazel#23127

The above flag is planned to be enabled by default in Bazel 8.0, which
is expected to be released on November 2024. Let's update our custom
repository rules so that they can continue working with Bazel 8.0.
@hiroyuki-komatsu hiroyuki-komatsu merged commit 8c8a446 into google:master Oct 16, 2024
1 check passed
@hiroyuki-komatsu
Copy link
Collaborator

We have merged your PR.
Thank you for the contribution!

@yukawa yukawa deleted the support_basel_23127 branch October 16, 2024 14:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants