Publish Gitea releases #22
Labels
No Label
Roadmap
V
bug
docs
duplicate
enhancement
good first issue
help wanted
idea
invalid
question
wontfix
Idea
Roadmap
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Depends on
#18 Create statically compiled binaries
vieter-v/vieter
Reference: vieter-v/vieter#22
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
Would be nice to publish releases that have both a tarball of the source code & a statically compiled binary, both for development & actual releases.
Considering the prod build already creates a static binary, we could use this to package everything into a release.
We can use the Gitea Release Plugin from Drone for this purpose. The idea would be to create a release that only contains the source code, & then add the static binaries for the various platforms to the release as they come in, using the Gitea API. Development releases could be of the form
x.y.z-n.hashwherex.y.zis the last created tag (or 0.0.0 if none is present yet), n is the amount of commits since this tag, & hash the hash of the commit.git rev-list --count HEAD ^maingives the amount commits made to the current branch since the last merge with main.git describe --tags --abbrev=0 2> /dev/null || echo '0.0.0'returns the newest tag, or0.0.0if none is present.The idea of publishing a release for every push to dev doesn't work, so we'll have to settle for just publishing releases when we create a new tag.