[GH-ISSUE #297] v1.13.1 Assets #50

Closed
opened 2026-02-26 18:33:04 +03:00 by kerem · 2 comments
Owner

Originally created by @SchnorcherSepp on GitHub (Jan 7, 2026).
Original GitHub issue: https://github.com/decke/smtprelay/issues/297

Could you please add the assets, just like in the other releases?

like [v1.13.0]
Assets 16
smtprelay-v1.13.0-freebsd-amd64.tar.gz
smtprelay-v1.13.0-freebsd-amd64.tar.gz.md5
smtprelay-v1.13.0-freebsd-arm64.tar.gz
smtprelay-v1.13.0-freebsd-arm64.tar.gz.md5
smtprelay-v1.13.0-linux-amd64.tar.gz
smtprelay-v1.13.0-linux-amd64.tar.gz.md5
smtprelay-v1.13.0-linux-arm64.tar.gz
smtprelay-v1.13.0-linux-arm64.tar.gz.md5
smtprelay-v1.13.0-windows-amd64.zip
smtprelay-v1.13.0-windows-amd64.zip.md5
smtprelay-v1.13.0-windows-arm64.zip
smtprelay-v1.13.0-windows-arm64.zip.md5
v1.13.0.tar.gz.asc
v1.13.0.zip.asc
Source code (zip)
Source code (tar.gz)

Originally created by @SchnorcherSepp on GitHub (Jan 7, 2026). Original GitHub issue: https://github.com/decke/smtprelay/issues/297 Could you please add the assets, just like in the other releases? like [v1.13.0] Assets 16 smtprelay-v1.13.0-freebsd-amd64.tar.gz smtprelay-v1.13.0-freebsd-amd64.tar.gz.md5 smtprelay-v1.13.0-freebsd-arm64.tar.gz smtprelay-v1.13.0-freebsd-arm64.tar.gz.md5 smtprelay-v1.13.0-linux-amd64.tar.gz smtprelay-v1.13.0-linux-amd64.tar.gz.md5 smtprelay-v1.13.0-linux-arm64.tar.gz smtprelay-v1.13.0-linux-arm64.tar.gz.md5 smtprelay-v1.13.0-windows-amd64.zip smtprelay-v1.13.0-windows-amd64.zip.md5 smtprelay-v1.13.0-windows-arm64.zip smtprelay-v1.13.0-windows-arm64.zip.md5 v1.13.0.tar.gz.asc v1.13.0.zip.asc Source code (zip) Source code (tar.gz)
kerem closed this issue 2026-02-26 18:33:04 +03:00
Author
Owner

@decke commented on GitHub (Jan 7, 2026):

No, because they are automatically build by the release action which did not fire. Don't know why and could not trigger it manually either. So well I probably have to do a 1.13.2 to see if it it's a permanent issue.

<!-- gh-comment-id:3719618452 --> @decke commented on GitHub (Jan 7, 2026): No, because they are automatically build by the release action which did not fire. Don't know why and could not trigger it manually either. So well I probably have to do a 1.13.2 to see if it it's a permanent issue.
Author
Owner

@decke commented on GitHub (Jan 7, 2026):

I implemented a manual trigger possibility for this action and triggered a rebuild. Looks okay now!

<!-- gh-comment-id:3719840759 --> @decke commented on GitHub (Jan 7, 2026): I implemented a manual trigger possibility for this action and triggered a rebuild. Looks okay now!
Sign in to join this conversation.
No labels
bug
pull-request
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
starred/smtprelay#50
No description provided.