Create release with prebuilt binary

[bessman]

Offering a prebuilt binary enables users to use alternative flashing methods, such as esptool.py.

[AsCress]

@bessman We can accomplish this through Github CI. Can you provide some information on what kind of artefacts are we looking for here, and how do we build them ?

[bessman]

The artifact we want to provide is ESP01Firmware.bin, which is already built in the compile.yml workflow. We can use action-gh-release to automatically attach it when we make releases.

[AsCress]

@bessman Is it built in compile.yml ? 🤔🤔
Not sure about that if the action we use stores the file anywhere. Let me have a look though.

[bessman]

Looking at compile-sketches, I can't immediately see a way to actually use the compiled artifacts.

We could change the build workflow to instead use https://github.com/plerup/makeEspArduino.

[bessman]

It should be possible to export binaries from compile-sketches using cli-compile-flags.

[AsCress]

@bessman Yes! I had observed the same thing, while writing this workflow. We should change the action that we use for building. I'll take care of this.

[AsCress]

It should be possible to export binaries from compile-sketches using cli-compile-flags.

Alright! Then, we should prefer that.