Magisk VS semver

Magisk (version 26.4): The Magic Mask

Magisk (version 26400): Companion app for Magisk

At this point download locally the Magisk APK onto your computer found here: https://github.com/topjohnwu/Magisk/releases. Reboot your Tab Mini C by holding the power button until you see the power come back on and the default power on screen begin loading. Once it has fully booted copy the Magisk APK, `boot_a.bin`, and `boot_b.bin` files via USB. Make certain to have backups of the `boot_a.bin` and `boot_b.bin` files in case something goes wrong (such as you bricking your device) and you need the old firmware. Install the Magisk APK. For the rest of this we will be following a summarized version of the instructions here: "https://topjohnwu.github.io/Magisk/install.html". Once the Magisk app is installed open it and press the "Install" button. Then click "Select and Patch a File" and select `boot_a.bin` then `boot_b.bin` files to install Magisk on both. At this point one should rename them to be `magisk_patched-boot_a.img` and `magisk_patched-boot_b.img` based on which one Magisk patched to make it easier for you. At this point transfer `magisk_patched-boot_a.img` and `magisk_patched-boot_b.img` back to the main computer over USB. Open up QFIL and once again run `adb reboot edl`. FAIRLY QUICKLY to avoid errors click the "Select Port" button and click the USB port which the Tab Mini C is plugged into and then click OK. Still quickly click "Tools" -> "Partition Manager" and then click OK on the popup. Within the partition manager find `boot_a` and `boot_b`. For each individually right click on the partition and then click "Manage Partition Data". Then click "Load Image" and point to the corresponding `magisk_patched-boot_a.img` and `magisk_patched-boot_b.img` depending on which partition you're patching. Once both of them are patched, quit out of QFIL. Force the reboot of the device by holding down the power button. Open the Magisk app and click on "Install" at which point their should be a new option "Direct Install". Use that to install directly onto the device after which it should give you the option to reboot. Reboot it and you now have a wonderfully rooted device. Happy reading

Install Magisk app onto your device: https://github.com/topjohnwu/Magisk/releases/download/v25.2/Magisk-v25.2.apk

Magisk Version: Magisk v26.2

Following the Semantic Versioning rules, you should raise the version number every time you need to publish your library. In your "package.json" file, you need to change the version number to reflect whether the changes are major, minor, or patch updates.

Semantic Versioning: An established convention for version numbers following the pattern MAJOR.MINOR.PATCH

Increases the major of the latest tag and prints it As per the Semver spec, it'll also clear the pre-release…

The reason for this is that software libraries and package managers, in general, but specifically here, rely on semantic versioning. Semantic versioning is really useful for distributing packages in a predictable way. What does this look like for our project?

For a more detailed and comprehensive guide on semantic versioning, visit https://semver.org

I believe neovim follows semantic versioning. https://semver.org/

Semver has been 2.0.0 for 10 years, look at the date of the assets. Multiple releases created today where none existed before. Not sure why someone is creating releases now, perhaps just some housekeeping/cleanup.

https://github.com/semver/semver/releases

All ELRS hardware will talk to all other ELRS hardware, including Radiomaster's ELRS transmitters and receivers. There are one or two exceptions from scummy companies that have been pilloried by the community, and you probably won't find them anymore. So long as the ELRS firmware running on both devices has the same major version number, you're good to go. ie. 3.3.1 will still talk to 3.0.1, but won't talk to 2.0.0. (The "major version" is the 1st number, the "minor version" is the 2nd number, and the "patch version" is the 3rd number. See Semantic Versioning for more info.)

If you're using semver, read the spec it's not overly long or hard to understand.

Semantic versioning actually has a clear rule about this: