Annotated tags are meant for releases while lightweight tags are meant
for private or temporary object labels.
For this reason, we should not trigger the automatic release actions
unless we have an annotated tag.
* Attempt cross compiling for apple silicon
* Try the apple expected compiler
* Make config.log viewable to figure out the compiler error
* Attempt to install the missing architecture
* Leave this branch in a working and documented what is missing state
* Try cross-compiling on macos with a specific SDK version
* Every now and again the runner pacakge db gets out of sync with reality - avoid this ever stopping a build, at the expense of making the builds take longer to run
* Add needed macos cross compile linker flag
* Fix package db sync for binaries build as well
* Add a fat binary build
* Add missing dep on the new binaries_macos_universal build
* Copy the macos cross compile artifacts into the right shared binaries bucket
* Use the correct arch-based subdir name for macos binaries
* Add workaround for 'truthy' warnings in yaml
See https://github.com/adrienverge/yamllint/issues/158
for some more discussion
* Check each yamllint line length warning and clearly markup those which cannot be easily folded into shorter lines
* Add a workflow to automatically upload packages in to tagged releases
* Mark automatic release as a pre-release as that way its contents are actually visible
* Dont run the release job unless we are acting on a tag
* Minor rename to try and fit description into github graph view
* Address shellcheck concerns with n2n_gateway.sh script
* Rename n2n_gateway.sh to live with all the other scripts (and update docs)
* Rename hack_fakeautoconf to make it clearly a shell script
* Address shellcheck concerns with hack_fakeautoconf.sh
* Rename python scripts to match other n2n tools
* Fix windows compile - when streamlining the use of hack_fakeautoconf.sh, I forgot to update all uses of this script
