kernel VS conventional-changelog

I will continue to work on fixing this error, but I am sure somebody knows what to do. The code I am referencing can be found at https://github.com/LibertyOS-Development/kernel

I set up a Discord server (https://discord.gg/CGZA85M8) and there is a GitHub repo for the kernel (https://github.com/LibertyOS-Development/kernel Star and share the repo pleeeeease)

If you want to see my operating system (it is built with Rust), you can find all the code on the GitHub page: https://github.com/LibertyOS-Development/kernel

The kernel: https://github.com/LibertyOS-Development/kernel

Using Conventional Commits ⭐ as a standard for your commit messages, makes Semantic Versioning 🔖 as easy as can be, with tools like Conventional Changelog 📄 Standard Version 🔖 and Semantic Release 📦🚀

conventional-changelog-conventionalcommits is a package used for creating conventional commits and has a bit more configuration possibilities with changelogs in contrast to the default Angular commit scheme.

Finally, it is also interesting to be able to automatically generate the CHANGELOG file from the commit messages. There are various tools for this, one of them is Conventional Changelog

Some projects generate change logs automatically from commits. For example, angular uses conventional-changelog.

I'm under the understanding from this issue that in semver, a package that is <1.0.0 is considered unstable. This means that a breaking change can occur at any version, usually between minors.

conventional-changelog-conventionalcommits

[1] - https://github.com/conventional-changelog/conventional-chang...

I dont use myself, but some people follows something like the conventional commit spec, and then uses a generator.