Conventional commit and semver bump helper
Paste the commit subjects since your last release, enter the current version and get the next semantic version, a validity check for each commit and a ready-to-paste changelog.
- Bump
- major
- Next version
- 2.0.0
- Commits
- 6 valid
- 1 not conventional
| Commit | Type | Scope | Breaking | Valid |
|---|---|---|---|---|
| feat(api): add cursor pagination to /orders | feat | api | yes | |
| fix(auth): refresh expired session tokens | fix | auth | yes | |
| perf(search): cache query plans | perf | search | yes | |
| docs: explain webhook retries | docs | - | yes | |
| refactor(db)!: drop legacy orders table | refactor | db | yes | yes |
| chore: bump dev dependencies | chore | - | yes | |
| update stuff | - | - | no |
Changelog
## 2.0.0
### Breaking changes
- **db:** drop legacy orders table
### Features
- **api:** add cursor pagination to /orders
### Bug fixes
- **auth:** refresh expired session tokens
### Performance
- **search:** cache query plans
Everything runs in your browser; nothing you type is sent anywhere.
How to use it
- Paste commit subjects, one per line, for example from git log --format=%s.
- Enter the current version. Tick the 0.x option if your project is below 1.0.
- Read the bump, the next version and the changelog. Fix commits marked invalid so tooling can read them.
Frequently asked questions
How does a commit map to a semver bump?
A breaking change (a ! after the type or a BREAKING CHANGE footer) bumps major, feat bumps minor, and fix or perf bumps patch. Other types do not release by themselves.
What does a valid commit look like?
type(scope)!: description, where scope and ! are optional, such as feat(api): add pagination or fix!: change the default timeout.
How does semver work below 1.0?
Anything can change before 1.0. Many tools shift one level down: breaking changes bump minor and features bump patch. Tick the option to match.
Which tools automate this?
semantic-release, release-please and commitlint all read Conventional Commits. This helper shows what they would do without installing anything.
Made by compiler.dev, faster GitHub Actions runners. More free tools.
Related tools
- CODEOWNERS generator and validatorWrite and validate a GitHub CODEOWNERS file. Catch invalid owners and unsupported patterns, and test which owners a file path resolves to.
- Dependabot config generatorGenerate a dependabot.yml for npm, pip, Docker, GitHub Actions, Go, Cargo and more, with schedule, grouping, labels and reviewers. Validated, copy-ready.
- DORA metrics calculatorCalculate the four DORA metrics from your deploy data and see if you rank Elite, High, Medium or Low on each, using the State of DevOps bands.
- GitHub Actions workflow YAML checkerPaste a GitHub Actions workflow and catch missing runs-on, unpinned actions, pull_request_target risks, missing permissions and bad needs.