helmsman VS semver

We've been using Helmsman (https://github.com/Praqma/helmsman) for the same use case. It supports some other creature comforts (automatic fetching of parameters from AWS SSM, chart ordering, etc.) and seems a bit more mature.

I've been using https://github.com/Praqma/helmsman for quite a few years now. Very pleased with it.

Have you looked at https://github.com/Praqma/helmsman ?

Kustomize manifests. Each microservice in its own folder. We have around 10 microservices, so it works for us. Db/metrics/monitoring/operators go into a Helmsman file.

I'm using Helmsman. It's a wrapper around Helm that allows you to inject environmental variables, amongst other things. It allows me to easily inject environmental variables from my Gitlab CI/CD into my Helm release.

Here's some issues where people asked the same question: https://github.com/Praqma/helmsman/issues/18 https://github.com/roboll/helmfile/issues/240

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: