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

[Bazel6] Upgrade to Bazel 6.0.0 #616

Merged

Conversation

@jerrymarino
Copy link
Contributor

@mattrobmattrob awesome stuff 👏 !

@mattrobmattrob mattrobmattrob force-pushed the mr/bazel.6.0.0.upgrade branch 7 times, most recently from 7e088ec to 0c31bf3 Compare December 5, 2022 17:38
@mattrobmattrob mattrobmattrob changed the title Work through Bazel 6.0.0 upgrade [Bazel6] Work through Bazel 6.0.0 upgrade Dec 6, 2022
@mattrobmattrob mattrobmattrob changed the title [Bazel6] Work through Bazel 6.0.0 upgrade [Bazel6] Upgrade to Bazel 6.0.0 Dec 7, 2022
@justinseanmartin
Copy link
Collaborator

After this change, CI will only validate against Bazel 6, right? If we're actively supporting Bazel 5 & Bazel 6, should we add a fork of the test configs that continues to run against Bazel 5?

@mattrobmattrob
Copy link
Collaborator Author

After this change, CI will only validate against Bazel 6, right? If we're actively supporting Bazel 5 & Bazel 6, should we add a fork of the test configs that continues to run against Bazel 5?

For sure, @justinseanmartin. I wanted to have a conversation with you all to determine what we want to do. I'm okay not merging this until we feel like "we support 6.0.0 and newer" is how we feel.

I'm hesitant to do much more in CI given those builds are already pretty slow/we're dealing with PR machine contention as it goes. But if you all are cool with it (you all are likely the majority of PR load at any time) then I'm happy to create a Bazel 6 test replication once it's officially released.

Copy link
Contributor

@jerrymarino jerrymarino left a comment

Choose a reason for hiding this comment

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

This seems to pass basic smoke tests on our end BTW ❤️ . I think it's reasonable to bump this onto 6.0 on CI given the worrysome 6.x.x changes are backwards compatible to a 5.x.x release. Someone will have to vet it more in-depth I think

The 6.0 release seems to be delayed but is coming soon - does it seem reasonable to merge it when we can get .bazelversion onto 6.0.0?

@mattrobmattrob
Copy link
Collaborator Author

The 6.0 release seems to be delayed but is coming soon - does it seem reasonable to merge it when we can get .bazelversion onto 6.0.0?

Thanks for testing it, @jerrymarino!

My preference is to move .bazelversion to 6.0.0 if we can, yeah. If you all are okay with it, I can get this PR in good shape once the release blockers are solved and 6.0.0 exists. 👍

@jerrymarino
Copy link
Contributor

SGTM overall!

@jerrymarino
Copy link
Contributor

@mattrobmattrob this looks awesome - and my understanding is we should be ready to land it.

Should we cut over to it 6.0 to celebrate the release drop that just happened?

@mattrobmattrob
Copy link
Collaborator Author

I already did, @jerrymarino 😊

@jerrymarino
Copy link
Contributor

That's great to hear - thanks again for making this happen! 👏 Should we land this bump of the version/project transitions then?

@jerrymarino jerrymarino marked this pull request as ready for review December 19, 2022 18:47
@mattrobmattrob
Copy link
Collaborator Author

That's great to hear - thanks again for making this happen! 👏 Should we land this bump of the version/project transitions then?

I'm good with it if you all are. 👍

Copy link
Collaborator

@luispadron luispadron left a comment

Choose a reason for hiding this comment

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

🚀

@jerrymarino
Copy link
Contributor

Yeah for sure 🚢 🎄!

@mattrobmattrob mattrobmattrob merged commit dfb604d into bazel-ios:master Dec 19, 2022
@mattrobmattrob mattrobmattrob deleted the mr/bazel.6.0.0.upgrade branch December 19, 2022 20:28
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.

None yet

4 participants