Create a file "SEMVER.md" which declares the public API of this product/project. See the Semantic Versioning specification item #1 for more information.
The "SEMVER.md" serves as a guideline for developers on how to determine if changes are considered to be major, minor, or patch, and ultimately how to resolve the next version number upon release.
Consider formatting commit messages accordingly to the Conventional Commits standard to be compatible with tooling for automatic changelog generation, e.g., standard-version/commit-and-tag-version.