versioning by abra vs goreleaser #77

Closed
opened 2021-09-07 07:18:35 +00:00 by knoflook · 1 comment
Owner

currently abra uses the version file to decide what version it is. Releases are versioned using tags though. We should only have one source for version though and I'd say that tags/commits are way better for that than a file sitting in the repo. When you're building abra during development (without tagging) it could use the latest commit hash as its version and add -dev at the end? We could do that, right?

currently abra uses the version file to decide what version it is. Releases are versioned using tags though. We should only have one source for version though and I'd say that tags/commits are way better for that than a file sitting in the repo. When you're building abra during development (without tagging) it could use the latest commit hash as its version and add -dev at the end? We could do that, right?
knoflook added this to the (deleted) milestone 2021-09-07 07:18:35 +00:00
knoflook added the
build
ci/cd
labels 2021-09-07 07:18:35 +00:00
Owner

Fully down for this! Use tags for goreleaser (drop the file) annnddd yeah, you'd just need to fiddle with the makefile for the local dev builds in 20fa0da1bb/Makefile (L5). Bear in mind, we do also have 20fa0da1bb/cmd/abra/main.go (L17)

Fully down for this! Use tags for goreleaser (drop the file) annnddd yeah, you'd just need to fiddle with the makefile for the local dev builds in https://git.coopcloud.tech/coop-cloud/go-abra/src/commit/20fa0da1bbafd2711362778d9b4a21b973f42bcf/Makefile#L5. Bear in mind, we do also have https://git.coopcloud.tech/coop-cloud/go-abra/src/commit/20fa0da1bbafd2711362778d9b4a21b973f42bcf/cmd/abra/main.go#L17
Sign in to join this conversation.
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: toolshed/abra#77
No description provided.