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

Use bazel 6 in the CI #1911

Merged
merged 6 commits into from
Jun 27, 2023
Merged

Use bazel 6 in the CI #1911

merged 6 commits into from
Jun 27, 2023

Conversation

ylecornec
Copy link
Member

Depends on #1909.

This PR updates the CI to bazel version 6.2.1
This is necessary to:

Some notes:

  • nixpkg is updated to a version that contains bazel 6.2.1.
  • The default go version for this version of nixpkgs is 1.20, which requires updating rules_go and rules_nixpkgs (to a version containing this fix).
  • With the nix setup, we now use the go toolchain from rules_go_configure instead of the host one. This is done in preparation for bzlmod because it is not possible to use is_nix_shell in the MODULE.bazel file.

@ylecornec ylecornec marked this pull request as ready for review June 19, 2023 16:47
@ylecornec ylecornec requested a review from avdv as a code owner June 19, 2023 16:47
Base automatically changed from ylecornec/incompatible_disable_starlark_host_transitions to master June 23, 2023 09:56
@dpulls
Copy link

dpulls bot commented Jun 23, 2023

🎉 All dependencies have been resolved !

- Use the same version of go with bindist as with nix
- Use go toolchain from rules_nixpkgs in preparation for bzlmod support because it is not possible to use `is_nix_shell` in the MODULE.bazel file
nodejs-16_x is deprecated in recent nixpkgs versions
This will become the default in bazel 7
@ylecornec ylecornec force-pushed the ylecornec/bazel_6 branch from 7a4889f to f15f0a9 Compare June 23, 2023 10:09
@ylecornec ylecornec mentioned this pull request Jun 26, 2023
Copy link
Member

@avdv avdv left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@ylecornec ylecornec added the merge-queue merge on green CI label Jun 27, 2023
@mergify mergify bot merged commit cdde0d0 into master Jun 27, 2023
@mergify mergify bot deleted the ylecornec/bazel_6 branch June 27, 2023 06:39
@mergify mergify bot removed the merge-queue merge on green CI label Jun 27, 2023
@@ -48,13 +48,12 @@ rules_proto_dependencies()
rules_proto_toolchains()

# For buildifier
# starting from 0.29, rules_go requires bazel >= 4.2.0
http_archive(
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ylecornec do you know which Bazel version rules_go 0.39.1 requires? AFAIK, 0.35 requires at least Bazel 5.1, so we might want to note somewhere that we require at least version x.y for developing on this repo? Or just use a .bazelversion file?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah indeed, it requires at least Bazel 5.3.

Release 0.38 is the one with the fix for incompatible_disable_starlark_host_transitions and requiring this version.

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.

Flag --incompatible_disable_starlark_host_transitions will break rules_haskell in Bazel 7.0
2 participants