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.

Sign up for GitHub

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

Jump to bottom

Flag --incompatible_config_setting_private_default_visibility will break rules_go in Bazel 7.0 #3386

Closed
keertk opened this issue Dec 7, 2022 · 1 comment · Fixed by #3387
Closed

Flag --incompatible_config_setting_private_default_visibility will break rules_go in Bazel 7.0 #3386

keertk opened this issue Dec 7, 2022 · 1 comment · Fixed by #3387

Comments

@keertk
Copy link
Member

keertk commented Dec 7, 2022 •
edited

Incompatible flag --incompatible_config_setting_private_default_visibility will be enabled by default in the next major release (Bazel 7.0), thus breaking rules_go. Please migrate to fix this and unblock the flip of this flag.

---> Note that this was not an issue until build #1349 and has been failing from #1351 onwards.

The flag is documented here: bazelbuild/bazel#12933.

Please check the following CI builds for build and test results:

Never heard of incompatible flags before? We have documentation that explains everything.
If you have any questions, please file an issue in https://github.com/bazelbuild/continuous-integration.
@keertk keertk mentioned this issue Dec 7, 2022
Open
@fmeum fmeum mentioned this issue Dec 7, 2022
Merged
@fmeum
Copy link
Collaborator

fmeum commented Dec 7, 2022

I created #3387 to fix this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

examples: Update rules_go version for incoming incompatible change bazelbuild/rules_go
2 participants
@fmeum @keertk