FYI @fmeum @ouillie

Here's an outline for how to verify if a solution will work for #1184:

Start by cloning @jarreds reproduction: https://github.com/jarreds/cel-go-repro.

Then, clone cel-spec locally, check out tag v0.15.0, apply the patches listed for that version in BCR, and use a local_path_override in the reproduction repo to bring cel-spec in from this local clone.

Here's what I know: if you edit go.mod in the local cel-spec clone, and change the module name at the top to anything other than cel.dev/expr, the build in the reproduction repo should start working. For instance, it works when you change it to module cel.dev/exp (missing the final 'r'). I cannot confidently tell you why that works, but I laid out my suspicion in #1184 (comment). Basically, I think it has to do with Gazelle getting confused by conflicting definitions for a Go module called cel.dev/expr.

It's possible that entirely ridding the cel-go repo of the Gazelle dependency on cel.dev/expr would also fix this. I left a comment to that effect.