Versioning is automated by semantic-release. There is no manual bump.
| branch | publishes | npm dist-tag | version shape |
|---|---|---|---|
dev |
every push with a feat:/fix:/perf: commit |
next |
0.2.0-dev.3 |
main |
every push (fast-forward from dev) |
latest |
0.2.0 |
Bump derived from commits since last tag on that branch:
fix:perf:→ patchfeat:→ minorfeat!:/BREAKING CHANGE:footer → majorchore:docs:refactor:test:ci:→ no release
chore(release): … commits are pushed back by the bot with [skip ci].
git switch main
git merge --ff-only dev
git push origin mainCI does the rest (tag, CHANGELOG.md, GitHub release, npm publish).
- Repo secret
NPM_TOKEN— npm Automation token with publish onherm-tui mainbranch created fromdev- Settings → Actions → Workflow permissions → Read and write
- Optional: branch protection on
mainmust allowgithub-actions[bot]to push (the@semantic-release/gitcommit)