Append go version to release/package file #1

Closed
opened 2024-06-24 00:38:25 +02:00 by leon · 3 comments
leon commented 2024-06-24 00:38:25 +02:00 (Migrated from git.leon.wtf)

Go plugins are built against a specific go version. If gotify updates it (like in 2.5.0), the plugin is incompatible. Since there might not be many changes to this tool, it should be possible to create multiple releases per version tag with different go version builds like 1.0.0-go1.22.0.

Luckily the masters go version is stored in build/gotify-server-go-version in the build job. We can use this to add the go version to the package registry path and to the release!

Go plugins are built against a specific go version. If gotify updates it (like in 2.5.0), the plugin is incompatible. Since there might not be many changes to this tool, it should be possible to create multiple releases per version tag with different go version builds like `1.0.0-go1.22.0`. Luckily the masters go version is stored in `build/gotify-server-go-version` in the build job. We can use this to add the go version to the package registry path and to the release!
leon commented 2024-06-24 00:38:26 +02:00 (Migrated from git.leon.wtf)

changed due date to July 23, 2024

changed due date to July 23, 2024
leon commented 2024-06-24 00:38:26 +02:00 (Migrated from git.leon.wtf)

assigned to @leon

assigned to @leon
leon commented 2024-06-24 14:29:25 +02:00 (Migrated from git.leon.wtf)

mentioned in merge request !4

mentioned in merge request !4
leon (Migrated from git.leon.wtf) closed this issue 2024-06-24 17:20:34 +02:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
leon/gotify-webhooks-plugin#1
No description provided.