ci: isolate riscv build failure from non-riscv merge jobs

[dictcp]

Summary

• Add a job-level if condition to the merge job so a build-riscv failure (e.g. RISE runner outage) only blocks the ubuntu2604 merge — all other targets (full, ubuntu2404, ubuntu2204, alpine) continue as long as build-amd64 and build-arm pass.

Before / after

Before: build-riscv failure → all 5 merge matrix jobs skipped
After: build-riscv failure → only ubuntu2604 merge skipped; other 4 targets unaffected

Condition logic

if: |
  always() &&
  needs.build-amd64.result == 'success' &&
  needs.build-arm.result == 'success' &&
  (matrix.target != 'ubuntu2604' || needs.build-riscv.result == 'success')

Test plan

• Simulate build-riscv failure and confirm full, ubuntu2404, ubuntu2204, alpine merge jobs still complete
• Confirm ubuntu2604 merge is correctly skipped when build-riscv fails

---

Generated by Claude Code

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: fe0d422df2

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Move matrix-dependent condition out of job if

In GitHub Actions, jobs.<job_id>.if is evaluated before strategy.matrix is applied, so matrix.target is not available in this job-level condition. In the inspected .github/workflows/main.yml merge job, this makes the new condition invalid or unable to distinguish ubuntu2604, so the workflow will not achieve the intended behavior of allowing the other merge targets to continue when build-riscv fails; split the merge jobs or move the target-specific gating to a place where the matrix context exists.

Useful? React with 👍 / 👎.