Task Summary
Today `Create and upload release candidate artifacts` (`create-release-candidate.yml`) only packages source/docker-compose tarballs from a tag — it doesn't compile the tagged commit or verify license-binary integrity. So an RC can be cut from a tag that doesn't actually build cleanly, or one with strict-mode license-binary drift.
Add a `build` job at the top of the RC workflow that calls the existing reusable `build.yml` with:
Make `create-rc` depend on `build` (`needs: build`), so we never produce an RC unless the tagged commit passes a full, strict build.
This closes a real gap with the parent license-binary effort (#4688): drift caught only by the nightly cron means it can land in an RC tagged before the next nightly. Wiring strict-build into the RC flow ensures the gate runs at the moment it matters.
Task Type
Task Summary
Today `Create and upload release candidate artifacts` (`create-release-candidate.yml`) only packages source/docker-compose tarballs from a tag — it doesn't compile the tagged commit or verify license-binary integrity. So an RC can be cut from a tag that doesn't actually build cleanly, or one with strict-mode license-binary drift.
Add a `build` job at the top of the RC workflow that calls the existing reusable `build.yml` with:
Make `create-rc` depend on `build` (`needs: build`), so we never produce an RC unless the tagged commit passes a full, strict build.
This closes a real gap with the parent license-binary effort (#4688): drift caught only by the nightly cron means it can land in an RC tagged before the next nightly. Wiring strict-build into the RC flow ensures the gate runs at the moment it matters.
Task Type