In Learn Guides, we sometimes want to point to the combined.bin for a particular board, for use with esptool.py or the Adafruit ESPTool. Right now we have to describe downloading the .zip and, unzipping it, and choosing the combined.bin, which is unlabeled. (Keeping track of anonymous combined.bin files is not easy. I often rename them or keep them in folders.)
The combined.bin is referenced far more often than anything else in the zip file. What would you think about uploading it separately, as a release artifact and/or to https://adafruit-circuit-python.s3.amazonaws.com/index.html?prefix=bootloaders/esp32/ ? It would be named something like tinyuf2-BOARDNAME-<version>-combined.bin, e.g. tinyuf2-adafruit_feather_esp32s2-0.32.0-combined.bin`.
EDIT: I will want to link to both combined.bin and combined-ota.bin, if they both exist.
In Learn Guides, we sometimes want to point to the combined.bin for a particular board, for use with esptool.py or the Adafruit ESPTool. Right now we have to describe downloading the .zip and, unzipping it, and choosing the
combined.bin, which is unlabeled. (Keeping track of anonymouscombined.binfiles is not easy. I often rename them or keep them in folders.)The
combined.binis referenced far more often than anything else in the zip file. What would you think about uploading it separately, as a release artifact and/or to https://adafruit-circuit-python.s3.amazonaws.com/index.html?prefix=bootloaders/esp32/ ? It would be named something liketinyuf2-BOARDNAME-<version>-combined.bin, e.g.tinyuf2-adafruit_feather_esp32s2-0.32.0-combined.bin`.EDIT: I will want to link to both
combined.binandcombined-ota.bin, if they both exist.