Summary

Replace the reusable go-release-workflow with a custom implementation to resolve conflicts with tagpr.

Background

The current release workflow fails with "a release with the same tag name already exists" error because:

1. tagpr automatically creates a GitHub release when a tag is pushed
2. The reusable workflow tries to create a new release with gh release create
3. This results in a conflict

Solution

Created a custom workflow that:

• Uses gh release upload instead of gh release create
• Waits for tagpr to create the release first (up to 5 minutes)
• Uploads built assets to the existing release
• Maintains all security features (cosign signing, attestation, SLSA provenance)

Changes

• Replaced reusable workflow with custom implementation based on https://github.com/suzuki-shunsuke/go-release-workflow
• Added wait logic for tagpr release creation
• Changed from creating new releases to uploading assets to existing releases
• Added GITHUB_TOKEN to all aqua-installer steps to avoid rate limits

Testing

This will be tested when the next release tag is pushed. The workflow should:

1. Wait for tagpr to create the release
2. Build and sign all assets
3. Upload assets to the existing release

Related

• Error log: https://github.com/yuya-takeyama/strict-s3-sync/actions/runs/16703244004/job/47277650819