semver
helmfile
Our great sponsors
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
semver
-
Using semantic-release to automate releases and changelogs
Semantic Versioning: An established convention for version numbers following the pattern MAJOR.MINOR.PATCH
-
Essential Command Line Tools for Developers
Increases the major of the latest tag and prints it As per the Semver spec, it'll also clear the pre-release…
-
Neovim v0.9.5 Released
I believe neovim follows semantic versioning. https://semver.org/
-
Semver 2.0.0 Released
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.
-
fkYAML v0.3.0: Support non-string-scalar nodes as mapping keys
If you're using semver, read the spec it's not overly long or hard to understand.
-
Immich will have breaking changes (again) in the next release
Semantic versioning actually has a clear rule about this:
-
Pragmatic Versioning – An Alternative to Semver
The biggest issue with semver is that it encourages compatibility breakages unoer a false promise that increased major version number saves the users from the dependency hell.
-
Python Versions and Release Cycles
Python versions include a major, minor, and micro component. It's slightly similar in concept to semver, though the minor version may do something incompatible at times. An example of this is the removal of distutils in 3.12. While technically not a language change persay, it did mean some build systems had to be revamped to accommodate this change. In general you'll see python referred to in a major.minor format such as:
helmfile
-
Deploy IRIS Application to Azure Using CircleCI
What we’re going to install into the newly created AKS cluster is located in the helm directory. The descriptive Helmfile approach enables us to define applications and their settings in the helmfile.yaml file.
-
[2022] [Updated] Alternative to Helmfile
Is there any alternative to https://github.com/roboll/helmfile you are currently using in your company.
-
Projectsveltos: Manage Kubernetes addons in multiple clusters
Interesting, I have approached this problem using Helmfile (https://github.com/roboll/helmfile) to define a “platform release package.”
-
How to Build Software Like an SRE
I agree; helm is too declarative.
Whenever I can, I use helmfile[0] for storing variables for helm since it does add a declarative layer on top of helm.
-
Managing multiple repos
helmfile is something i’ve used in the past for this https://github.com/roboll/helmfile
-
Helm is both "package manager" and "templating engine" - probably the best package manager but horrible template engine
I always felt like dependencies in helm are for very simple non-coupled packages. I many times use Helmfile (https://github.com/roboll/helmfile) to manage dependencies instead of banging my head with vanilla Helm.
-
So I've installed grafana, loki, and prometheus on the personal Kubernetes cluster via Terraform. Now what?
Once you do that, learn to create dynamic helm charts that use go templating and conditionals: https://github.com/roboll/helmfile
-
Interesting tools?
helmfile is not widely known but awesomeme
-
How to keep track of 3d party applications helm chart on K8S?
Not exactly an answer to your question, but we have created a separate project called "cluster" where we define all cluster dependencies via https://github.com/roboll/helmfile, meaning that you always know what (+versions) you have in the cluster and can easily reproduce it. It does not solve an issue with knowing what project has a new version now but at least you can be sure what version is in your cluster
-
Requesting guidance. Helm deployment and structure.
Dont.Use.Umbrella.Charts. If you need to deploy multiple things at once, but you dont wanna deal with relative complexity of Flux or ArgoCD - use helmfile. https://github.com/roboll/helmfile
What are some alternatives?
flux2 - Open and extensible continuous delivery solution for Kubernetes. Powered by GitOps Toolkit.
cdk8s - Define Kubernetes native apps and abstractions using object-oriented programming
helmsman - Helm Charts as Code
kustomize - Customization of kubernetes YAML configurations
helm-operator - Successor: https://github.com/fluxcd/helm-controller — The Flux Helm Operator, once upon a time a solution for declarative Helming.
terraform - Terraform enables you to safely and predictably create, change, and improve infrastructure. It is a source-available tool that codifies APIs into declarative configuration files that can be shared amongst team members, treated as code, edited, reviewed, and versioned.
react-native - A framework for building native applications using React
helm - The Kubernetes Package Manager
argocd-image-updater - Automatic container image update for Argo CD
terraform-provider-flux - Terraform provider for bootstrapping Flux
semantic-release - :package::rocket: Fully automated version management and package publishing
helmwave - New 🌊 wave for @helm