Skip to content

ci(release): publish tagged binary assets#36

Merged
edithatogo merged 1 commit into
masterfrom
codex/release-asset-publishing
Jul 12, 2026
Merged

ci(release): publish tagged binary assets#36
edithatogo merged 1 commit into
masterfrom
codex/release-asset-publishing

Conversation

@edithatogo

Copy link
Copy Markdown
Owner

Summary

  • publish all six cross-platform binary and checksum artifacts to tagged GitHub Releases
  • retain tagged go install version verification

Validation

  • workflow YAML parses
  • git diff --check

@gemini-code-assist

Copy link
Copy Markdown

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

@amazon-q-developer amazon-q-developer Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review Summary

This PR adds binary asset publishing to GitHub Releases, which is a valuable addition to the release workflow. However, there are two critical issues that will prevent the workflow from functioning:

  1. Missing checkout step in the publish job - the gh release create command requires repository context
  2. Artifact version mismatch between upload (v7) and download (v5) actions will cause artifact retrieval to fail

These issues must be fixed before merge to ensure the release workflow executes successfully.

The permission change from read to write is appropriate for publishing release assets.


You can now have the agent implement changes and create commits directly on your pull request's source branch. Simply comment with /q followed by your request in natural language to ask the agent to make changes.

if: startsWith(github.ref, 'refs/tags/v')
needs: binaries
runs-on: ubuntu-latest
steps:

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛑 Logic Error: gh release create requires repository context but no checkout step exists. This will cause the command to fail with "not a git repository" error when accessing $GITHUB_REPOSITORY and attempting to create the release.

Suggested change
steps:
steps:
- uses: actions/checkout@v7

needs: binaries
runs-on: ubuntu-latest
steps:
- uses: actions/download-artifact@v5

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛑 Compatibility Issue: Version mismatch between upload-artifact@v7 (line 73) and download-artifact@v5 causes artifact retrieval failure. Artifacts uploaded with v7 are incompatible with v5 download action.

Suggested change
- uses: actions/download-artifact@v5
- uses: actions/download-artifact@v7

@edithatogo edithatogo merged commit 6d40a64 into master Jul 12, 2026
10 checks passed
@edithatogo edithatogo deleted the codex/release-asset-publishing branch July 12, 2026 13:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant