ci: #3 Add binaries to Releases

[miquelbeltran]

ci: #3 Add binaries to Releases

Description 📝

• Purpose: This GitHub Actions workflow automatically builds binaries and uploads them to each release when a release is created.

• Approach: The job is triggered on release creation, it checkouts the release tag, then builds binaries for Linux, MacOS and Windows, then uploads them to the release that triggered the action.

• Related to Distribute binaries (so no Dart SDK is required) #3 but does not close it, because we still need a way to distribute updates

Type of change

• CI improvement

Updates

• Created release.yaml file

Screenshots 📷

Test plan 🧪

Tested in a fork, the resulting files can be seen here: https://github.com/miquelbeltran/raygun-cli/releases/tag/0.0.6

Author to check 👓

• Project and all contained modules builds successfully
• Self-/dev-tested
• Unit/UI/Automation/Integration tests provided where applicable
• Code is written to standards
• Appropriate documentation written (code comments, internal docs)

Reviewer to check ✔️

• Project and all contained modules builds successfully
• Change has been dev-/reviewer-tested, where possible
• Unit/UI/Automation/Integration tests provided where applicable
• Code is written to standards
• Appropriate documentation written (code comments, internal docs)

[TheRealAgentK]

Looks good! And if individual builds cause issues, we can fine-tune as we go.