A small fix to how we ship updates
A previous update failed to go out because of a release pipeline issue. That's fixed now, and nothing else changes for you.
The previous update failed to publish because of a runtime mismatch on the server that builds and ships SharpOS. We've pinned that process to the same Node version our main systems already use, so it runs the same way every time.
Nothing in the product changes here. It's entirely about making sure future updates go out reliably.