Onboard AI learns any GitHub repo in minutes and lets you chat with it to locate functionality, understand different parts, and generate new code. Use it for free at www.getonboard.dev. Learn more →
Semver Alternatives
Similar projects and alternatives to semver
-
semantic-release
:package::rocket: Fully automated version management and package publishing
-
standard-version
:trophy: Automate versioning and CHANGELOG generation, with semver.org and conventionalcommits.org
-
InfluxDB
Collect and Analyze Billions of Data Points in Real Time. Manage all types of time series data in a single, purpose-built database. Run at any scale in any environment in the cloud, on-premises, or at the edge.
-
lerna
:dragon: Lerna is a fast, modern build system for managing and publishing multiple JavaScript/TypeScript packages from the same repository.
-
-
-
changesets
🦋 A way to manage your versioning and changelogs with a focus on monorepos
-
-
Onboard AI
Learn any GitHub repo in 59 seconds. Onboard AI learns any GitHub repo in minutes and lets you chat with it to locate functionality, understand different parts, and generate new code. Use it for free at www.getonboard.dev.
-
-
-
-
-
-
gitflow
Git extensions to provide high-level repository operations for Vincent Driessen's branching model.
-
-
-
-
-
-
-
storybook
Storybook is a frontend workshop for building UI components and pages in isolation. Made for UI development, testing, and documentation.
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
semver reviews and mentions
-
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:
- We Have to Talk About Flask
-
Automate NPM releases on GitHub using changesets 🦋
Changesets follow semantic versioning conventions. In a nutshell, this indicates that the version number follows the fixed format of major.minor.patch. A patch is a backwards-compatible bugfix, a minor is a feature that is backwards compatible, and a major is for any change that isn't backwards compatible.
- Semantic Versioning 2.0.0 – Semantic Versioning
-
Long Term Ownership of an Event-Driven System
Keeping dependencies up to date is crucial for the long-term health and security of your system. Regularly updating dependencies ensures that you benefit from upstream bug fixes, performance improvements, and security patches. If a library you are using uses Go modules, it will likely be using SEMVER to help both humans and machines figure out the impact of making a change. Semver promotes the following notation:
-
macOS Containers v0.0.1
Oh, it was easier than I thought: https://semver.org/#spec-item-2
A normal version number MUST take the form X.Y.Z where X, Y, and Z are
-
Helm-Compose – The Docker-compose like tool for K8s development
> Helmfile complies to Semantic Versioning 2.0.0 in which v0.x means that there could be backward-incompatible changes for every release.
You're not following semver if your software is used in production, and you recommend using it in production, but you label it 0.x.
I hate this cowardice of "we believe in semver" and "we stick to the area of it where everything goes, the exact thing it was created to avoid".
-
A note from our sponsor - Onboard AI
getonboard.dev | 8 Dec 2023