You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
chore(flagd): protobuf modules are only generated by a build #446
The flagd provider's protobuf modules are generated only by the hatch-protobuf build hook, so nothing importable exists until a distribution is built.
Two consequences:
CI runs uv build for every package on every Python version, purely so this one package gets its generated modules.
CONTRIBUTING.md still tells contributors to run hatch build once and to test with hatch test. Both predate the move to uv, and hatch is not a dependency of the repo any more, so following the instructions fails.
Generating code is a test input, not an artifact of the build (pypa/hatch#1824). The flagd testkit already handles this correctly: hatch_build_sync.py is an ordinary script, poe test runs it first, and the build hook only ships what it produced. The flagd provider should do the same for protoc.
Activity