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

Bump to rules_scala-6.5.0, update repo name patch #322

Merged
merged 1 commit into from
Jul 8, 2024

Conversation

mbland
Copy link
Contributor

@mbland mbland commented Jul 8, 2024

Details:

Removes the part of the patch that worked around the removal of to_proto and to_json members from a struct, since this version contains a fix:

Updates the remaining part of the patch to define
_unmangle_bzlmod_repo_name. This is in anticipation of the Bazel maintainers replacing ~ as the canonical repo name format delimiter due to build performance issues on Windows:

I plan to see about contributing this function to bazelbuild/bazel-skylib eventually.

Details:

- https://github.com/bazelbuild/rules_scala/releases/tag/v6.5.0

Removes the part of the patch that worked around the removal of
`to_proto` and `to_json` members from a struct, since this version
contains a fix:

- bazelbuild/rules_scala#1554

Updates the remaining part of the patch to define
`_unmangle_bzlmod_repo_name`. This is in anticipation of the Bazel
maintainers replacing `~` as the canonical repo name format delimiter
due to build performance issues on Windows:

- bazelbuild/bazel#22865

Signed-off-by: Mike Bland <[email protected]>
@mbland mbland self-assigned this Jul 8, 2024
@mbland mbland merged commit 74ceabf into main Jul 8, 2024
4 checks passed
@mbland mbland deleted the bzlmod-rules_scala-6.5.0-patch branch July 8, 2024 18:25
@jayconrod
Copy link
Contributor

This is in anticipation of the Bazel maintainers replacing ~ as the canonical repo name format delimiter due to build performance issues on Windows

Ah, that's why they're replacing ~? Now I'm curious why that causes issues on Windows and at what layer. So many things could be bad and broken.

@benjaminp
Copy link
Contributor

bazelbuild/bazel#22865

@mbland
Copy link
Contributor Author

mbland commented Jul 8, 2024

bazelbuild/bazel#22865

That's in the PR/commit description, too. 🙂

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.

3 participants