Consider RCs equivalent to release for bazel_compatibility#19678
Closed
fmeum wants to merge 1 commit intobazelbuild:masterfrom
Closed
Consider RCs equivalent to release for bazel_compatibility#19678fmeum wants to merge 1 commit intobazelbuild:masterfrom
bazel_compatibility#19678fmeum wants to merge 1 commit intobazelbuild:masterfrom
Conversation
We want `bazel_compatibiliy = [">=6.4.0"]` to match `6.4.0rc1` so that release candidates are indistinguishable from the actual release via Bazel version compatibility requirements. This allows more realistic testing of releases via RCs without having users to rely on hacks such as `bazel_compatibility = [">=6.3.9999"]`. Along the way change the error message on incompatibility to include the standard module key identifier, which is `<root>` for the root module instead of `<name>@<version>`, both of which can be empty.
Collaborator
Author
|
@bazel-io flag |
github-actions
bot
added
awaiting-review
bazel-io
added
the
potential release blocker
meteorcloudy
added
awaiting-PR-merge
Member
|
@bazel-io fork 6.4.0 |
bazel-io
removed
the
potential release blocker
github-actions
bot
removed
the
awaiting-PR-merge
bazel-io
pushed a commit
to bazel-io/bazel
that referenced
this pull request
Oct 2, 2023
We want `bazel_compatibiliy = [">=6.4.0"]` to match `6.4.0rc1` so that release candidates are indistinguishable from the actual release via Bazel version compatibility requirements. This allows more realistic testing of releases via RCs without having users to rely on hacks such as `bazel_compatibility = [">=6.3.9999"]`. Along the way change the error message on incompatibility to include the standard module key identifier, which is `<root>` for the root module instead of `<name>@<version>`, both of which can be empty. Closes bazelbuild#19678. PiperOrigin-RevId: 569982709 Change-Id: I7dce89ac1c62c1539d71704f048dca65232c119c
iancha1992
pushed a commit
that referenced
this pull request
Oct 2, 2023
…19689) We want `bazel_compatibiliy = [">=6.4.0"]` to match `6.4.0rc1` so that release candidates are indistinguishable from the actual release via Bazel version compatibility requirements. This allows more realistic testing of releases via RCs without having users to rely on hacks such as `bazel_compatibility = [">=6.3.9999"]`. Along the way change the error message on incompatibility to include the standard module key identifier, which is `<root>` for the root module instead of `<name>@<version>`, both of which can be empty. Closes #19678. Commit 21cd4ef PiperOrigin-RevId: 569982709 Change-Id: I7dce89ac1c62c1539d71704f048dca65232c119c Co-authored-by: Fabian Meumertzheim <[email protected]> Co-authored-by: Yun Peng <[email protected]>
Member
|
The changes in this PR have been included in Bazel 6.4.0 RC2. Please test out the release candidate and report any issues as soon as possible. If you're using Bazelisk, you can point to the latest RC by setting USE_BAZEL_VERSION=last_rc. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We want
bazel_compatibiliy = [">=6.4.0"]to match6.4.0rc1so that release candidates are indistinguishable from the actual release via Bazel version compatibility requirements. This allows more realistic testing of releases via RCs without having users to rely on hacks such asbazel_compatibility = [">=6.3.9999"].Along the way change the error message on incompatibility to include the standard module key identifier, which is
<root>for the root module instead of<name>@<version>, both of which can be empty.