Versioning policy
policies/versioningEdited since a person last confirmed it (confirmed 2026-10-03, edited 2026-10-28)
reopened
Written 2026-10-28 by ktl-librarian (automation). Last checked 2026-10-03 by noelmcloughlin (a person).
The full record
- Checks
- 2026-10-29 by
ktl-librarian(automation) - 2026-09-10 by
noelmcloughlin(a person) - 2026-09-26 by
noelmcloughlin(a person) - 2026-10-03 by
noelmcloughlin(a person)
- 2026-10-29 by
- Review by
- 2027-10-03
- Sources
docs/releasing.mddocs/architecture.mdCONTRIBUTING.mdCHANGELOG.md.github/workflows/publish.yml.releaserc.json.github/workflows/semantic-release.ymlhttps://github.com/semantic-release/commit-analyzer/blob/v13.0.1/README.mdhttps://github.com/semantic-release/commit-analyzer/blob/v13.0.1/lib/default-release-rules.jshttps://github.com/conventional-changelog/conventional-changelog/blob/conventional-changelog-conventionalcommits-v8.0.0/packages/conventional-changelog-conventionalcommits/src/parser.js
- Related to
- Pointed to by
- Releasing (references)
- Why the skills live in their own repository (references)
- Graph
- Open this concept in the knowledge graph
- IRI
https://w3id.org/ktl/knowledge/policies/versioning- Licence
- CC BY 4.0
- Files
- MarkdownJSON-LDSource on GitHubHistory on GitHub
Overview
Section titled “Overview”vMAJOR.MINOR.PATCH. Since 0.15.0 (2026-09-12, CHANGELOG.md) the bump is computed from Conventional Commits, and nobody picks a version number.
docs/releasing.md gives the bump for each type: feat: is minor, fix: and security: are patch, and a BREAKING CHANGE: footer or ! after the type is major. docs:, chore:, refactor:, style:, test: and ci: release nothing: the change is merged, and its changelog entries are released with the next release that does.
The configuration agrees with that page on ! since 0.57.0.1 .releaserc.json names the Conventional Commits preset ("preset": "conventionalcommits"), and semantic-release.yml pins conventional-changelog-conventionalcommits@8.0.0 beside @semantic-release/commit-analyzer@13.0.1. That preset’s header pattern allows a ! after the type, so a feat!: or fix!: commit gives a major release, as a BREAKING CHANGE: note does. The workflow’s comment says the preset is named because the default, Angular, does not read the !. The analyzer’s default rules also give perf: and a revert a patch, and .releaserc.json adds security: as a patch. The plan job in semantic-release.yml counts a commit with ! as one that would release.
All six skills are released together under one tag rather than versioned independently, so a set pinned to one tag agrees with itself (docs/architecture.md).
One asymmetry to know: tags carry a v prefix (v0.16.0), and publish.yml refuses a version typed without it, while CHANGELOG.md headings never do (## [0.16.0]). The workflow’s cross-check strips the v before comparing the two.
Footnotes
Section titled “Footnotes”-
CHANGELOG.md, 0.57.0, Fixed ↩