Conversation
Member
|
Can you include also which version should users upgrade to? |
Contributor
Author
Good idea, done! |
Wyverald
approved these changes
Jun 30, 2023
|
This is breaking bazel's CI: https://buildkite.com/bazel/bazel-bazel-github-presubmit/builds/16408 and all other builds on master since this landed. The problem seems to be introduced with bazel's |
werkt
added a commit
to werkt/bazel-central-registry
that referenced
this pull request
Jul 2, 2023
This reverts commit e91124a.
|
With further guidance that |
werkt
added a commit
to werkt/bazel
that referenced
this pull request
Jul 2, 2023
bazelbuild/bazel-central-registry#725 broke bazel CI asynchronously by yanking rules_go@0.34.0, listed as a dependency on BCR of grpc@1.48.1. From BCR recommendation on bazelbuild/bazel-central-registry#733, specifying a rules_go@0.38.1 should coerce transitive selection through Minimum Version Selection.
werkt
added a commit
to werkt/bazel
that referenced
this pull request
Jul 2, 2023
bazelbuild/bazel-central-registry#725 broke bazel CI asynchronously by yanking rules_go@0.34.0, listed as a dependency on BCR of grpc@1.48.1. From BCR recommendation on bazelbuild/bazel-central-registry#733, specifying a rules_go@0.39.1 should coerce transitive selection through Minimum Version Selection.
copybara-service bot
pushed a commit
to bazelbuild/bazel
that referenced
this pull request
Jul 3, 2023
bazelbuild/bazel-central-registry#725 broke bazel CI asynchronously by yanking rules_go@0.34.0, listed as a dependency on BCR of grpc@1.48.1. From BCR recommendation on bazelbuild/bazel-central-registry#733, specifying a rules_go@0.39.1 should coerce transitive selection through Minimum Version Selection (and bypass gazelle@0.27.0, also yanked). Closes #18828. PiperOrigin-RevId: 545205842 Change-Id: I574fc46b7c09e72e6d70ef77be726897aacc4358
fweikert
pushed a commit
to fweikert/bazel
that referenced
this pull request
Jul 12, 2023
bazelbuild/bazel-central-registry#725 broke bazel CI asynchronously by yanking rules_go@0.34.0, listed as a dependency on BCR of grpc@1.48.1. From BCR recommendation on bazelbuild/bazel-central-registry#733, specifying a rules_go@0.39.1 should coerce transitive selection through Minimum Version Selection (and bypass gazelle@0.27.0, also yanked). Closes bazelbuild#18828. PiperOrigin-RevId: 545205842 Change-Id: I574fc46b7c09e72e6d70ef77be726897aacc4358
fweikert
added a commit
to bazelbuild/bazel
that referenced
this pull request
Jul 12, 2023
bazelbuild/bazel-central-registry#725 broke bazel CI asynchronously by yanking rules_go@0.34.0, listed as a dependency on BCR of grpc@1.48.1. From BCR recommendation on bazelbuild/bazel-central-registry#733, specifying a rules_go@0.39.1 should coerce transitive selection through Minimum Version Selection (and bypass gazelle@0.27.0, also yanked). Closes #18828. PiperOrigin-RevId: 545205842 Change-Id: I574fc46b7c09e72e6d70ef77be726897aacc4358 Co-authored-by: George Gensure <werkt0@gmail.com>
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.
These version were marked as experimental, which resulted in print warnings whenever their module files are evaluated. As they are still discovered starting from modern versions of these rulesets, the warnings ended up affecting all users.
By yanking these versions, Bazel 6.3.0 and later will no longer emit the warnings.