fix(release): develop to main - #839
Conversation
The primary build now passes require_build_identity: true to build.yml unconditionally, so a primary Dockerfile without ARG REVISION fails the release instead of publishing an image that cannot prove its version and commit. The input stays, defaults to true, and only sets the default for extra_builds groups; a group without a Go binary opts out with "require_build_identity": false. build.yml is unchanged. Floating tier-* consumers receive the rule on promotion; fixed pins on their next bump.
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Repository: LerianStudio/github-actions-shared-workflows/.coderabbit.yml Review profile: ASSERTIVE Plan: Essentials Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
🔍 Lint Analysis
|
🔍 PR Validation Summary✅ PR Mergeable — no blocking failures
|
🛡️ CodeQL Analysis ResultsLanguages analyzed: Found 1 issue(s): 1 Medium
🔍 View full scan logs | 🛡️ Security tab |
|
@coderabbitai approve |
✅ Action performedComments resolved and changes approved. |
Release: develop to main
Ships #838:
go-releaserequires the compiled build identity on every primary image by default (require_build_identitydefaults totrue). A caller opts out per image group with"require_build_identity": false; a non-Go group needs that opt-out.Who is affected
Swept every caller of
go-release.ymlondevelopandmain(research/wave-d-consumer-sweep.mdin the identity-mandatory plan):tier-*caller and every fixed pin ondevelopalready passesrequire_build_identity: true, so the new default changes nothing for them.tier-2) has not adopted yet; matcher fix(go-pr-validation): expose and forward filter_paths and path_level #467 pins it tov1.76.0beforetier-2is promoted.tier-1) is GoReleaser-only and never runs the image job.tier-0) and billing-worker (tier-2) adopted ondeveloponly; their stable releases are cut before the tier they sit on is promoted.Promotion order
tier-0promotes on this release.tier-1andtier-2wait for approval, andtier-2waits for matcher #467 and the billing-worker stable release.🤖 Generated with Claude Code