-
Notifications
You must be signed in to change notification settings - Fork 118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
use releases for bootloaders? #43
Comments
Hi @mkinney |
Sources would be great, but not necessary. That'd be awesome if they were added to a "manual" release. Thank you! |
Also, please let me know when you get rid of the existing link for that zip as I'll need to change it, too. :-) |
Pushed a manual release, please check. Not sure what you mean with
|
Wow. That was fast. Ignore my last question about the existing link. I'll change to the release file. Can you add one more thing? Can you add the info to the release note? (or at least the "Date"):
and the INFO_UF2.TXT file, too? |
Otherwise, that release https://github.com/RAKWireless/WisBlock/releases/tag/0.4.2 looks great! |
Ok, I will close this then. Anyway we try to NOT update the bootloader too often. Only if there is a bug. |
Looking at the download https://github.com/RAKWireless/WisBlock/blob/master/bootloader/RAK4630/Latest/WisCore_RAK4631_Board_Bootloader.zip
from the https://github.com/RAKWireless/WisBlock/tree/master/bootloader/RAK4630 page.
Perhaps that zip file should be pushed to a release?
If the CI cannot build them (due to some internal reason, you can always create a release manually and push the files into it). If you do have the steps, but need help adding them to your CI, share the steps, and I'll see if I can help adding it.
I'm planning on consuming that Bootloader in the meshtastic-flasher tool ( see https://github.com/meshtastic/Meshtastic-gui-installer ) and I'd prefer having a stable endpoint with version. In other words, I'd like to know that bootloader release 1.2.3 has a date of xxx and SoftDevice version yyy when I query the INFO_UF2.TXT file.
The text was updated successfully, but these errors were encountered: