A Git plugin for managing semantic versioning tags with a plugin architecture for CHANGELOG.md and package.json.
Git Semantic Versioning is a Git plugin that automates the creation and management of semantic version tags in Git repositories. It helps developers adhere to Semantic Versioning 2.0.0 by providing commands to increment major, minor, patch, pre-release, and build versions, reducing manual errors and ensuring consistency.
Developers and DevOps engineers who manage versioning for software projects, especially those using Git and needing automated semantic versioning with integrations for changelogs and package managers.
It offers a lightweight, plugin-based approach to semantic versioning directly within Git, with support for dry runs, flexible configuration, and optional plugins for tools like Keep a Changelog and NPM, making it a versatile alternative to manual version tagging.
Git plugin for Semantic Versioning
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Automatically creates Git tags following semantic versioning rules, reducing manual errors and ensuring consistency. For example, commands like 'git semver major' increment versions correctly.
Supports plugins for tools like Keep a Changelog and NPM package.json, allowing integration into existing workflows. The README details plugins in PLUGINS.md.
Enables previewing version changes with the --dryrun flag before creating tags, helping avoid mistakes. This is shown in usage examples like 'git semver patch --dryrun'.
Configuration files can be set at repository, user, or system levels, as described in the Configuration section, allowing tailored behavior for different projects.
Only a few built-in plugins are available, and creating custom ones requires shell scripting knowledge, which may not suit teams needing broader tool integration.
Requires cloning and running install.sh scripts, which can be insecure or cumbersome compared to package manager installations, as noted in the Installation section.
Exclusively works within Git repositories, making it unsuitable for projects using other version control systems or needing standalone version management.