SemVer Bumper
Parse and increase Semantic Versioning
Parsed parts
1MAJOR
4MINOR
2PATCH
–Pre-release
–Build
Breaking changes
2.0.0New features (backward compatible)
1.5.0Bug fixes (backward compatible)
1.4.3Pre-release label
1.4.2-alpha.1Remove pre-release
1.4.2Format: MAJOR.MINOR.PATCH[-pre-release][+build]
• MAJOR: Incompatible API changes
• MINOR: New backward-compatible functionality
• PATCH: Backward-compatible bug fixes
Semantic Versioning Management
The SemVer Bumper tool simplifies the process of managing software versioning by following standard semantic versioning rules. It allows you to parse complex version strings including major, minor, and patch components, as well as optional pre-release labels and build metadata. By providing clear categorization for breaking changes versus backward-compatible features and bug fixes, the tool helps developers maintain consistent release cycles and clearly communicate the impact of every update to their users through accurate version numbering.
Secure Browser-Based Processing
Your data remains private because the SemVer Bumper operates directly within your web browser. No version strings are sent to a server or stored in a database, ensuring that your internal project identifiers and release notes stay local. This makes it an ideal tool for developers who need to quickly calculate next versions without exposing sensitive metadata. The tool provides instant results while maintaining the highest standards of security and privacy for your software development workflow.
Frequently asked questions
How does SemVer Bumper help with release notes?
The tool helps you categorize changes into breaking changes, new features, or bug fixes. This distinction is crucial for semantic versioning because it determines whether the version should be bumped at the major, minor, or patch level, ensuring your users always know what to expect from every update.
Can I include pre-release tags and build metadata?
Yes, the SemVer Bumper supports full semantic versioning specifications. You can include optional pre-release identifiers like alpha or beta, as well as build metadata in your version strings. The tool parses these components correctly, allowing you to manage complex release cycles with precision and accuracy.
What happens when I bump a version?
When you select an action to increase the minor or patch number, the tool automatically calculates the correct version string. It handles the logic of resetting lower-level numbers while maintaining your specific pre-release tags where applicable, ensuring that your next release follows standard conventions perfectly.