semver VS semantic-release

version: Your package's current version. It's best practice to follow semantic versioning (semver).

Tags should follow the Semantic Versioning standard because it is easy-to-follow and well-documented.

After implementing your CI/CD jobs, a release using semantic versioning has to be created to be available on the CI/CD Catalog.

Semver, defined by the specification https://semver.org/, is a versioning scheme designed to convey meaning about underlying code changes. A version number MAJOR.MINOR.PATCH indicates:

Relevant section: https://semver.org/#:~:text=How%20should%20I,next%20major%20...

Cargo uses Semantic Versioning, a convention for versioning that helps manage updates and compatibility. Here’s a quick breakdown:

Semantic Versioning: Adopts the SemVer specification, with version formats like vX.Y.Z (major.minor.patch), clearly defining version compatibility.

Developers have been afraid of 1.0.0 for a while, in defiance of the semver spec [1], but being afraid of 0.1.0 is a whole new level. Wtf. I guess 0.1 has become the new 1.0 after years of mis-versioning.

Those coreutils are being included in Ubuntu, call them 1.0! It's fine, you still have a countable infinity of version numbers if you need to make changes, even incompatible ones!

[1]: https://semver.org/#how-do-i-know-when-to-release-100

> If your software is being used in production, it should probably already be 1.0.0. If you have a stable API on which users have come to depend, you should be 1.0.0. If you’re worrying a lot about backward compatibility, you should probably already be 1.0.0.

Out of curiosity, what's the difference between this and semantic versioning[0]?

[0]https://semver.org/

> Having commits prefixed by "chore:" or "docs(ui):" aren't that useful.

I don't use those for humans, I use those for tooling, such as semantic-release. The human-readable bits come after that.

https://semantic-release.gitbook.io/

See also: semantic-release

In the simplest form, it means that we create one repository with a bunch of sub-directories for our projects and libraries (packages) and that's it. The rest stays as it is: pushing to the origin, publishing with npm or Lerna. Maybe even with semantic-release if you already made some optimization of the process.

Because conventional commits add a consistent prefix to your commit messages, automated tools can parse this prefix and use it for other nice things. One of these things is making your project follow the Semantic Versioning specification by automatically creating semantic releases. The screenshot below shows how pretty your generated release documentation becomes by using conventional commmits:

Unlike https://github.com/semantic-release/semantic-release , plugin https://github.com/TheUnderScorer/nx-semantic-release pre-starts building a dependency graph between libraries and applications, and then starts the release process for all related code.

semantic-release: Fully automatic; you can integrate it into GitHub CI to automatically update the version code and publish to npm each time you update your code on GitHub.