ci: release automation with GoReleaser #22
Conversation
Use the long form instead.
WalkthroughEnhancing software development workflows through efficient updates to GitHub Actions workflows and GoReleaser configurations for streamlined version control, deployment, and testing processes. Changes
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #22 +/- ##
=======================================
Coverage 35.79% 35.79%
=======================================
Files 13 13
Lines 556 556
=======================================
Hits 199 199
Misses 343 343
Partials 14 14 ☔ View full report in Codecov by Sentry. |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
Review Details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (3)
- .github/workflows/release.yaml (1 hunks)
- .github/workflows/test.yaml (1 hunks)
- .goreleaser.yaml (1 hunks)
Files skipped from review due to trivial changes (2)
- .github/workflows/release.yaml
- .github/workflows/test.yaml
Additional comments not posted (6)
.goreleaser.yaml (6)
3-13: The build configuration looks good and covers common platforms and architectures.
15-16: Checksum configuration is appropriately set with a clear and standard naming convention.
18-20: Archive configuration is correctly set with a dynamic naming template that enhances clarity.
22-24: Changelog configuration is well-set using GitHub's native tools and logical sorting order.
26-27: Release configuration smartly uses automatic determination for pre-releases, which is a good use of automation.
30-65: Container configuration is well-defined, using a secure base image and appropriate tagging rules. Ensure the tagging logic works as expected in different scenarios.Verification successful
The tagging logic in the
.goreleaser.yamlfile has been verified and is correctly implemented to handle both release and pre-release scenarios as intended. The use of conditional tags ensures appropriate behavior depending on the release type.
.goreleaser.yaml: Correctly uses conditional logic for tagging in different release scenarios.Scripts Executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify the tagging logic in different scenarios. # Test: Search for the tagging logic usage. Expect: Correct behavior in both release and pre-release scenarios. rg --type yaml $'tags:'Length of output: 49
Script:
#!/bin/bash # Description: Examine the tagging logic in `.goreleaser.yaml` to ensure it behaves correctly in both release and pre-release scenarios. # Display the lines around the 'tags:' entry to understand the logic applied. rg --type yaml --context 10 'tags:' .goreleaser.yamlLength of output: 540
There was a problem hiding this comment.
Actionable comments posted: 0
Review Details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (3)
- .github/workflows/release.yaml (1 hunks)
- .github/workflows/test.yaml (1 hunks)
- .goreleaser.yaml (1 hunks)
Files skipped from review as they are similar to previous changes (3)
- .github/workflows/release.yaml
- .github/workflows/test.yaml
- .goreleaser.yaml
There was a problem hiding this comment.
Actionable comments posted: 0
Review Details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (3)
- .github/workflows/release.yaml (1 hunks)
- .github/workflows/test.yaml (1 hunks)
- .goreleaser.yaml (1 hunks)
Files skipped from review as they are similar to previous changes (3)
- .github/workflows/release.yaml
- .github/workflows/test.yaml
- .goreleaser.yaml
There was a problem hiding this comment.
Actionable comments posted: 0
Review Details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (3)
- .github/workflows/release.yaml (1 hunks)
- .github/workflows/test.yaml (1 hunks)
- .goreleaser.yaml (1 hunks)
Files skipped from review as they are similar to previous changes (3)
- .github/workflows/release.yaml
- .github/workflows/test.yaml
- .goreleaser.yaml
Publishes to GitHub and DockerHub using GoReleaser.
The workflow publishes when
v*style tags are built: release secrets use GitHub tag and deployment environment protection.Container images are based on the Chainguard Static container and run as non-root. They are published to the
chinmina/chinmina-bridgerepository.Closes #13
Summary by CodeRabbit
New Features
Chores
chinmina-bridgebinary across various platforms.