lukaszraczylo 116ba9b006 fix: add missing condition to release job to prevent skipping ...

Problem:
- Release job (merge phase) was being skipped even though all builds succeeded
- The shared workflow's release job has `needs: [version, build]` but no `if` condition
- Without `if: always()`, GitHub Actions skips the job if dependencies have non-success status
- Frontend job being skipped caused downstream effects

Solution:
- Created local copy of go-release-cgo.yaml workflow
- Added explicit condition to release job:
  if: |
    always() &&
    needs.version.result == 'success' &&
    needs.build.result == 'success'
- Updated release.yaml to use local workflow instead of remote

This ensures the release/merge phase runs as long as version and build jobs succeed,
regardless of optional jobs like frontend being skipped.

Note: This is a workaround until the fix is merged upstream in shared-actions repo.

2026-01-03 22:57:21 +00:00

..

autoupdate.yaml

Initial commit

2026-01-02 23:14:23 +00:00

go-release-cgo-local.yaml

fix: add missing condition to release job to prevent skipping

2026-01-03 22:57:21 +00:00

pr.yaml

Initial commit

2026-01-02 23:14:23 +00:00

release.yaml

fix: add missing condition to release job to prevent skipping

2026-01-03 22:57:21 +00:00