Skip to content

Remove bazel 6 from CI and testing#244

Open
furtib wants to merge 3 commits into
Ericsson:mainfrom
furtib:drop-bazel-6
Open

Remove bazel 6 from CI and testing#244
furtib wants to merge 3 commits into
Ericsson:mainfrom
furtib:drop-bazel-6

Conversation

@furtib

@furtib furtib commented Jun 16, 2026

Copy link
Copy Markdown
Contributor

Why:
We have previously agreed that as long as we keep the WORKSPACE files working, we can drop support for bazel 6.
Since we encountered issues where Bazel 6 compatibility can only support a subset of features, we decided not to maintain Bazel 6 in a half-working state but rather drop it entirely.

What:

  • Removed bazel 6 from CI

Addresses:
none

@furtib furtib requested a review from Szelethus June 16, 2026 09:47
@furtib furtib self-assigned this Jun 16, 2026
@furtib furtib closed this Jun 16, 2026
@furtib furtib changed the title Explicitly drop support for bazel 6 Set minimum bazel verwsion in MODULE.bazel Jun 17, 2026
@furtib furtib changed the title Set minimum bazel verwsion in MODULE.bazel Set minimum bazel version in MODULE.bazel Jun 17, 2026
@furtib furtib reopened this Jun 18, 2026
@furtib furtib changed the title Set minimum bazel version in MODULE.bazel Remove bazel 6 from CI Jun 18, 2026
@furtib furtib changed the title Remove bazel 6 from CI Remove bazel 6 from CI and testing Jun 18, 2026
@@ -1,5 +1,4 @@
[
"6.5.0",

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

I'm sure we do not need this file at all :)

Comment thread MODULE.bazel
Comment on lines +17 to +19
module(
name = "rules_codechecker",
)

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Any reason for this change?

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