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

Add a potential problems check to make sure no .bazelversion is used. #2300

Merged

Conversation

hzeller
Copy link
Collaborator

@hzeller hzeller commented Dec 15, 2024

.bazelversion is a very crude bazel feature that does not support semantic versioning, let alone version ranges. In combination with baselisk, it even attempts to download binaries from the 'net instead of using system-available versions.

Instead of pinning a bazel version, the repo should be kept in a state, that it works with all actively maintained bazel versions.

.bazelversion is a very crude bazel feature that does not support
semantic versioning, let alone version ranges. In combination with
baselisk, it even attempts to download binaries from the 'net instead
of using system-available versions.

Instead of pinning a bazel version, the repo should be kept in a state,
that it works with all actively maintained bazel versions.
@hzeller hzeller merged commit 7452cde into chipsalliance:master Dec 16, 2024
34 checks passed
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.

1 participant