Add note in the docs about possibly high costs for macOS GitHub runners

[mipastgt]

In your documentation you recommend to build everything together via a matrix of GitHub runners. However, this may be a costly approach if you use a free account combined with private repositories. The notarization of macOS apps takes quite some time and with a normal setup you are billed for all this waiting time. This is especially important because macOS runners are already 10x more expensive than Linux runners for example. Maybe you should add a warning note to the documentation, so that people are aware of this.
See attached file for some more details.

github-runners.txt

[kdroidFilter]

Thanks for raising this — it's a fair point worth contextualizing.

While macOS runners are indeed more expensive than Linux ones, it helps to put the numbers in perspective. Even a team releasing once a day (~10 min of macOS runner time per release) would stay well under what commercial alternatives charge just for access to their packaging solution — solutions that are often less complete than what Nucleus provides.

That said, runner costs are ultimately a CI/CD management concern that falls within the developer's responsibility, regardless of what tool they're using. For teams with very high release frequency, a self-hosted runner on a Mac Mini (plugged into a home router or a small server) is an excellent and cost-effective option that sidesteps the billing concern entirely.

We could add a brief note in the docs mentioning this tradeoff and pointing to the self-hosted runner option as an alternative — but I'd want to frame it as practical advice rather than a warning, since the cost profile is quite reasonable for the vast majority of use cases.

[mipastgt]

A brief note is all what I have suggested :-) Nevertheless I would like to point out that, if one release takes 10 minutes, it's 20 minutes for x86+ARM x 10 = 200 minutes. That is you can make only 10 such releases per month and I haven't even counted in the extra time for Linux and Windows. Self hosted runners seem to be a must in such a scenario.