-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ci: Add goreleaser workflow #2040
ci: Add goreleaser workflow #2040
Conversation
ff72790
to
2d46850
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #2040 +/- ##
===========================================
+ Coverage 73.84% 73.90% +0.06%
===========================================
Files 248 248
Lines 24801 24801
===========================================
+ Hits 18312 18328 +16
+ Misses 5226 5213 -13
+ Partials 1263 1260 -3
Flags with carried forward coverage won't be shown. Click here to find out more. see 8 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
39d307a
to
46e0373
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
## Relevant issue(s) Resolves sourcenetwork#2039 ## Description This PR adds a Goreleaser workflow to automate the publication of releases on Github and DockerHub. Note that the release header and the milestone name should be updated manually for every release.
Relevant issue(s)
Resolves #2039
Description
This PR adds a Goreleaser workflow to automate the publication of releases on Github and DockerHub.
Note that the release header and the milestone name should be updated manually for every release.
This is what the release would look like on Github:
Tasks
How has this been tested?
With Goreleaser locally and through the CI on my defradb fork.
Specify the platform(s) on which this was tested: