Missing hex for v2.1.0-beta.1

[aivarannamaa]

Congratulations for the new release!

The hex-file seems to be missing from https://github.com/microbit-foundation/micropython-microbit-v2/releases/tag/v2.1.0-beta.1. Is it following soon?

[microbit-carlos]

Thanks!

Yes, it's there now, had some issues with the system that built it from the tag last night:

• https://github.com/microbit-foundation/micropython-microbit-v2/releases/tag/v2.1.0-beta.1
• https://github.com/microbit-foundation/micropython-microbit-v2/releases/download/v2.1.0-beta.1/micropython-microbit-v2.1.0-beta.1.hex

[microbit-carlos]

Ah, the same is true with the V1 beta release:

• https://github.com/bbcmicrobit/micropython/releases/tag/v1.1.0-beta.1

Do you load the hex file from Thonny? Do you keep both hex files individually or use a Universal Hex?

[aivarannamaa]

Do you load the hex file from Thonny? Do you keep both hex files individually or use a Universal Hex?

There is an online json that Thonny consults for finding the firmware. V1 and V2 have separate entries, so for Thonny it doesn't really matter if there is an universal hex available.

https://github.com/bbcmicrobit/micropython/releases/download/v1.1.0-beta.1/microbit-micropython-v1.1.0-beta.1.hex and https://github.com/microbit-foundation/micropython-microbit-v2/releases/download/v2.1.0-beta.1/micropython-microbit-v2.1.0-beta.1.hex are both specific to micro:bit version, right?

[aivarannamaa]

I'm going to add v1.1.0-beta.1 and v2.1.0-beta.1 as download options to this online json I mentioned before. The first download option gets preselected when the user opens the flashing dialog.

Would you recommend setting the new versions as default / preselected options or leave them as secondary options for now?

[microbit-carlos]

We'll be adding the beta versions of MicroPython to the beta version of the Python editor, but not the "live" one:
https://python.microbit.org/v/beta

So we consider them stable, but some of the new V2 API in this release (datalogging, SoundEffects, power, etc) might be tweaked before the final release, so programmes created with the beta API might not work in the final release.

Apart from that nothing should be broken, except for a couple of outstanding things in the new power module, but that's the thing that might be tweaked the most before release (or if we find any blockers there, we might pull the power module from the 2.1.0 release and only have it available in betas).

So I guess it's up to you how stable/experimental you'd like the default.

[aivarannamaa]

I added the new betas as secondary download options for now.

[microbit-carlos]

Sounds good, thanks!
Shouldn't take too long for the final releases to be out 👍