Skip to content

Revert "Yank obsolete rules_go and gazelle versions"#733

Closed
werkt wants to merge 1 commit intobazelbuild:mainfrom
werkt:revert-725-fmeum-patch-1
Closed

Revert "Yank obsolete rules_go and gazelle versions"#733
werkt wants to merge 1 commit intobazelbuild:mainfrom
werkt:revert-725-fmeum-patch-1

Conversation

@werkt
Copy link
Copy Markdown

@werkt werkt commented Jul 2, 2023

Reverts #725

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 have failed due to a grpc@1.48.1 -> rules_go@0.34.0 chain. The rules_go version may be fluid enough to change for grpc, but since CI guards against this with "Existing modules should not be changed" checks, bazel CI will be broken until a new version of grpc is released to BCR and bazel is made to depend upon it, for which there may not be an upstream version that is compatible without further changes to bazel core.

@fmeum
Copy link
Copy Markdown
Contributor

fmeum commented Jul 2, 2023

Since Bzlmod uses Minimum Version Selection, it should suffice to temporarily add a bazel_dep on rules_go in a non-yanked version to Bazel's MODULE.bazel file.

After CI is green again, we can add a new, BCR-only version of grpc (with a .bcr.1 version suffix) that depends on a new version of rules_go, update the grpc pin in Bazel and remove the direct rules_go dep.

@fmeum
Copy link
Copy Markdown
Contributor

fmeum commented Jul 2, 2023

Cc @Wyverald

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.
@werkt
Copy link
Copy Markdown
Author

werkt commented Jul 2, 2023

rules_go is similarly afflicted with gazelle at the recommended 0.38.1. Trying for 0.39.1 which moves the bar on gazelle to 0.30.0

@werkt
Copy link
Copy Markdown
Author

werkt commented Jul 2, 2023

bazel CI green for bzlmod builds with bazelbuild/bazel#18828: rules_go@0.39.1

@fmeum
Copy link
Copy Markdown
Contributor

fmeum commented Jul 2, 2023

Thanks for the report and PR!

As discussed above, let's fix this forward with #734 and your Bazel PR.

@fmeum fmeum closed this Jul 2, 2023
@werkt werkt deleted the revert-725-fmeum-patch-1 branch July 2, 2023 12:36
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>
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