-
Notifications
You must be signed in to change notification settings - Fork 34
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
audit artifact autodetection for use with go-releaser #197
Comments
Hey! Thank you so much! Do you have binaries or do you have to use the go installer. If so we also support any package manager |
Seems there is no test for that whatsoever and the docs are still in progress but you can use:
Instead of cargo dist true, let me know if there is something i am missing |
I plan to add binaries using GitHub release, abd brew / snap / aur packages |
@pomdtr i know it's been a bit but i'm looking into this and adding support for it- does goreleaser generate a manifest for the assets it builds? |
Not sure it is what you are looking for, but goreleaser returns checksum.txt file : see https://github.com/deta/space-cli/releases/tag/v0.3.1 |
After running goreleaser locally, I found out that it generates an [
{
"name": "sunbeam",
"path": "/Users/achille/Developer/github.com/pomdtr/sunbeam/dist/sunbeam_darwin_arm64/sunbeam",
"goos": "darwin",
"goarch": "arm64",
"internal_type": 4,
"type": "Binary",
"extra": {
"Binary": "sunbeam",
"Ext": "",
"ID": "sunbeam"
}
},
// ...
] |
@pomdtr !!! this is excellent. having this file will make it very easy for oranda to generate what it needs to. does goreleaser give you an option to also publish that file to github releases? |
I'm not sure, but it looks like you can publish extra files in the release step: Here is the link to the doc: https://goreleaser.com/customization/release/ I'm currently tuning the goreleaser setup for sunbeam, i'll take a look! |
Hi, love your work on this.
I'm considering using this tool for my golang project (https://github.com/pomdtr/sunbeam),
however it looks like the installation screen can only be generated for cargo-dist projects.
What are your opinion on adding support for other releasers ?
The text was updated successfully, but these errors were encountered: