[email protected]

[mmorel-35]

Release: https://github.com/bazelbuild/rules_fuzzing/releases/tag/v0.5.1

Closes #1728

[bazel-io]

Hello @bazelbuild/bcr-maintainers, modules without existing maintainers (rules_fuzzing) have been updated in this PR. Please review the changes.

[fmeum]

Thanks for the contribution! @stefanbucur is currently working on the last steps for setting up the automated BCR publishing flow for rules_fuzzing. Let's wait for a bit before we add this manually.

[mmorel-35]

Will it's work apply with 0.5.1 or is this going to need a new version ?
If it requires a new version, this one can be added or am I missing something ?

[fmeum]

If it requires a new version, this one can be added or am I missing something ?

That's true, but we need to ensure that the next release is API compatible. That's why I would at least want to wait for @stefanbucur's approval.

[mmorel-35]

Any news from @stefanbucur ?

[meteorcloudy]

I chatted with @stefanbucur, he probably don't have capacity to actually maintain this BCR module, and in future, we'll probably move rules_fuzzing to bazel-contrib.

[fmeum]

@meteorcloudy Would he be okay with me becoming the BCR maintainer?

[meteorcloudy]

Yes, that's definitely fine!

[stefanbucur]

Yes, that's definitely fine!

+1, I think Fabian would be most qualified to maintain rules_fuzzing moving forward. Nowadays I have very little time on my end and I often am the bottleneck in reviewing & approving PRs too.

[fmeum]

@mmorel-35 Could you add my contact info (you can get it from rules_go) here instead of Stefan's? You also have to exclude the replay test as it pulls in googletest. Then we can merge this, thanks for working on it!

[mmorel-35]

@fmeum ,
How do you ship/ignore a target ?

[keith]

would be great if we could merge this so i could use it in #1807

[stefanbucur]

would be great if we could merge this so i could use it in #1807

@fmeum Is there something on my end that you folks are blocked on?

[fmeum]

@stefanbucur No, I just didn't realize that this was updated and the checks were failing.

Bazel 6 support is lacking due to a bug fixed by bazel-contrib/rules_fuzzing#248, but this can wait for a new release. Testing the main repo itself was buggy for various reasons, but that's to be expected. Just testing the test module makes more sense and that works.

[keith]

thanks!