Conversation
Agents and users integrating the Bazel module routinely misread the declared `eigen 3.4.0.bcr.3` dependency as a pin and conclude the library only works with old Eigen. Under bzlmod it is a minimum: version selection resolves to the highest Eigen requested anywhere in the module graph, and every BCR eigen release from 3.4.0 through 5.x shares compatibility_level 1. Make this explicit in the README integration section and next to the bazel_dep itself, and add a dedicated workflow that appends a single_version_override for the newest BCR Eigen 5 release and runs the full test suite, so the compatibility claim stays verified as new Eigen versions land. The override is appended in CI rather than committed because single_version_override is only honored in the root module and would otherwise force the pin on consumers.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Agents and users integrating the Bazel module routinely misread the declared
eigen 3.4.0.bcr.3dependency as a pin and conclude the library only works with old Eigen. Under bzlmod it is a minimum: version selection resolves to the highest Eigen requested anywhere in the module graph, and every BCR eigen release from 3.4.0 through 5.x shares compatibility_level 1.Make this explicit in the README integration section and next to the bazel_dep itself, and add a dedicated workflow that appends a single_version_override for the newest BCR Eigen 5 release and runs the full test suite, so the compatibility claim stays verified as new Eigen versions land. The override is appended in CI rather than committed because single_version_override is only honored in the root module and would otherwise force the pin on consumers.