-
Notifications
You must be signed in to change notification settings - Fork 357
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 riegeli 0.0.0-20241218-3385e3c #3502
Conversation
@bazel-io skip_check unstable_url This version is required by ArrayRecord
@bazel-io skip_check unstable_url |
Hello @QrczakMK, modules you maintain (riegeli) have been updated in this PR. Please review the changes. |
Co-authored-by: Fabian Meumertzheim <[email protected]>
Require module maintainers' approval for newly pushed changes.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello @bazelbuild/bcr-maintainers, all modules in this PR have been approved by their maintainers. Please take a final look to merge this PR.
Unfortunately riegeli doesn't build on 8.x.
Head branch was pushed to by a user without write access
Require module maintainers' approval for newly pushed changes.
@QrczakMK we need your approval again because I made a change to lock bazel to 7.x. (one of the upstream package lzma/xz doesn't build with 8.x) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would be great to fix lzma so that it builds with bazel 8.x.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello @bazelbuild/bcr-maintainers, all modules in this PR have been approved by their maintainers. Please take a final look to merge this PR.
This version is required by ArrayRecord
Last PR attempt didn't work because I needed to add
@bazel-io skip_check unstable_url
in the PR comment.