Drop bazel 6.x support #2610
Merged
Drop bazel 6.x support #2610
Conversation
This file contains 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
With 8.x out imminently, the number of permutations to support bazel changes and legacy linking behavior in bazel 6.x is getting too costly.
keith
requested review from
aaronsky,
BalestraPatrick,
brentleyjones,
luispadron,
mattrobmattrob and
thii
as code owners
luispadron
approved these changes
Dec 5, 2024
brentleyjones
approved these changes
Dec 5, 2024
mattrobmattrob
approved these changes
Dec 5, 2024
|
Should we get a release with any of the commits in main right now before merging this? |
|
Yeah, sounds good. |
|
sorry i had automerge enabled first. there aren't that many commits so i don't think it's worth reverting to juggle creating that |
|
We can make a branch from before this and cut the release from that. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
With 8.x out imminently, the number of permutations to support bazel
changes and legacy linking behavior in bazel 6.x is getting too costly.