GoReleaser
-
|
https://goreleaser.com/customization/sign/ says:
but I'm unclear how to set that up in the configuration. I have a tool that has Thanks. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 6 replies
-
|
Something like this, probably: signs:
- signature: "${artifact}.sig"
cmd: your-tool-name
args: ["--in", "${artifact}", "--out", "${signature}"] |
Beta Was this translation helpful? Give feedback.
-
|
what do you think about this: #5018 ? |
Beta Was this translation helpful? Give feedback.
-
|
@caarlos0 I appreciate you taking the time to implement a new pipeline to support signing of binaries. Unfortunately, for my use-case, I don't think it helps. If I'm trying to build a tool for three different OSes (linux, windows, darwin), the code signing requirements are slightly different for each. I'm not code-signing the linux binary and, for the other two OSes, the command-line tool I'm using needs a parameter that specifies which sort of binary blob is being signed. So I need to pass a different value to the command-line tool depending on the OS I'm building for. I realise that this is very much an edge case for how goreleaser is being used, so I would not expect you to have that level of flexibility. To solve this for my own needs, I've created separate sections in the build pipeline, one for each OS, allowing me that flexibility when calling the code signing tool. |
Beta Was this translation helpful? Give feedback.
-
|
this is something I have been planning to do, but haven't yet. for now, you'll need multiple builds unfortunately |
Beta Was this translation helpful? Give feedback.
-
|
fwiw, |
Beta Was this translation helpful? Give feedback.
fwiw,
binary_signsis onmain, and in goreleaser pro you also have aifoption to further select which binaries to signhttps://goreleaser.com/customization/binary_sign/