DanielStormApps
Release build on CI producing final binary artifact
Thank you for a very useful app! Especially now.
It would be really nice to have binaries built and attached to GitHub releases on git tags.
That would simplify package management maintenance as each binary would have a uniq URL.
It should be quite easy to add a GitHub Action doing just that, so if you perceive there is a value in all this - I will be happy to give it a try.
My pleasure!
Could you elaborate on attaching the binary to the release tag? Have an example repo that does this already?
I’m not positive if CI is possible with Apple requiring Notarization now. But I’ve never really looked into it.
Any detailed information you can provide on what this workflow would solve and any examples of a similar integration would be greatly appreciated 🙂
The suggestions was just to apply a good engineering practice of versioning binary release artefacts, so https://github.com/DanielStormApps/Fanny/releases/tag/2.3.0 would have a .zip \w .app automatically built by CI on pushing a git tag.
Example https://github.com/mLupine/SoundflowerBed/releases/tag/2.0.0-release
Automated notarisation, if desired, seems to to be possible to archive as well.