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

[7.3.0] Add flag --incompatible_use_plus_in_repo_names #23141

Merged
merged 1 commit into from
Jul 29, 2024

Conversation

bazel-io
Copy link
Member

Defaults to false. When set to true, we use + instead of ~ as the separator in canonical repo names.

Some more subtle changes include:

  • We now officially say that the "build" part of version strings (the part that begins with a plus) is ignored and stripped.
  • When the flag is set to true, we effectively increase the lockfile version by 1 (see code comment in BazelLockFileModule).
  • When true, we no longer insert a _main in front of names of repos generated by module extensions hosted in the main repo. (~abc as a name was problematic, but +abc is not.)
  • When true, we no longer insert a v in front of numerical versions in canonical repo names. (my_mod~1.1 could be a Windows short path, but my_mod+1.1 cannot.)

Work towards #22865.

Closes #23103.

PiperOrigin-RevId: 657202616
Change-Id: I015b2a04a823b1d951015a1b2e1b99b154dcc5a2

Commit 2f67e57

Defaults to false. When set to true, we use `+` instead of `~` as the separator in canonical repo names.

Some more subtle changes include:
- We now officially say that the "build" part of version strings (the part that begins with a plus) is ignored and stripped.
- When the flag is set to true, we effectively increase the lockfile version by 1 (see code comment in BazelLockFileModule).
- When true, we no longer insert a `_main` in front of names of repos generated by module extensions hosted in the main repo. (`~abc` as a name was problematic, but `+abc` is not.)
- When true, we no longer insert a `v` in front of numerical versions in canonical repo names. (`my_mod~1.1` could be a Windows short path, but `my_mod+1.1` cannot.)

Work towards bazelbuild#22865.

Closes bazelbuild#23103.

PiperOrigin-RevId: 657202616
Change-Id: I015b2a04a823b1d951015a1b2e1b99b154dcc5a2
@bazel-io bazel-io requested a review from a team as a code owner July 29, 2024 15:40
@bazel-io bazel-io added team-ExternalDeps External dependency handling, remote repositiories, WORKSPACE file. awaiting-review PR is awaiting review from an assigned reviewer labels Jul 29, 2024
@iancha1992 iancha1992 removed the request for review from fmeum July 29, 2024 15:42
@iancha1992 iancha1992 added this pull request to the merge queue Jul 29, 2024
Merged via the queue into bazelbuild:release-7.3.0 with commit 5f5355b Jul 29, 2024
52 checks passed
@github-actions github-actions bot removed the awaiting-review PR is awaiting review from an assigned reviewer label Jul 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
team-ExternalDeps External dependency handling, remote repositiories, WORKSPACE file.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants