error-message-index VS semver

Significant effort is going into resolving this issue right now and things should be much improved in 9.6. We already have https://errors.haskell.org/ which catalogues many errors with descriptions and examples. The asspciated error codes will be added to all errors once 9.6 is release for easy reference.

We're also delighted to announce integration with errors.haskell.org, which already has a couple of GHCup codes documented, e.g. https://errors.haskell.org/messages/GHCup-00010/

To support the Haskell Foundation’s Haskell Error Index initiative, all Stack error messages generated by Stack itself begin with an unique code in the form [S-nnnn], where nnnn is a four-digit number.

I don't think the resolved issues are actually ones about error messages. They largely seem to be meta issues about the project. As far as I know nothing that project has done has made it into a released GHC yet, but GHC 9.6 will have unique error codes for each error pointing to an entry on https://errors.haskell.org/. Both the codes and the website are achievements of that project, specifically under its error-messages-index incarnation. If you'd like to contribute you may like to read https://github.com/haskellfoundation/error-message-index/blob/main/CONTRIBUTING.md or post a message introducing yourself on https://github.com/haskell/error-messages/issues/new.

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: