Marlin_Ender3v2 VS semver

From what I'm reading, mriscoc's firmware appears to be a bit more polished and offers even more features than Jyers. Have a look at their page - https://github.com/mriscoc/Marlin_Ender3v2/releases/latest From what I'm reading you can change the bed dimensions via gcode command and also in the advanced settings menu. I'm going to try this route despite having already downloaded all the software to compile my own jyers firmware..

Download the bin file from here https://github.com/mriscoc/Marlin_Ender3v2/releases/latest.

By any chances are you using the Jyers firmware? Because that firmware works horrible with a lot of probes. Try the Professional Firmware, I never had a probe crashing problem with that one.

Once you tram the bed, are you doing a mesh? I use UBL (Unified Bed Leveling) to do a 15x15 mesh that takes approximately 225 points of readings. If you are using Jyers firmware, which I highly recommend) or Professional firmware by mriscoc, both rimwares based on Marlin but are more rich in features than the base Marlin firmware, you can view the mesh on your display and see where the high/low spots are. The mesh can be saved to your EEPROM and used without having to redo the leveling process all the time. This is, of course, providing that your bed is not shifting and you wait for the bed to cool down before removing the prints so it doesn't mesh of the leveling. I am not sure about the Professional firmware (because I don't use that one) but I do know the Jyers firmware has a bunch of precompiled .bin files for all the boards and for many different configurations.

https://github.com/Jyers/Marlin/releases or https://github.com/mriscoc/Marlin_Ender3v2/releases

I am using a modified Jyers firmware from here: https://github.com/mriscoc/Marlin_Ender3v2

i use https://github.com/mriscoc/Marlin_Ender3v2 and i am very happy with it

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: