Commits and versioning
Write Conventional Commits whose type, scope, and breaking marker drive Semantic Versioning; see how release-please turns merged commits into a human-approved Release-PR, changelog, and tag; and how the trunk-based, protected-main model gates every release.
Units5
Duration28 min
Levelintermediate
By the end of this module, you'll be able to:
- Write a Conventional Commits 1.0.0 message -
<type>[scope][!]: <desc>- and choose the type, scope, and breaking marker deliberately. - Explain how commit types drive Semantic Versioning:
featto MINOR,fixto PATCH, a break to MAJOR, and how pre-1.0 changes that rule. - Describe how release-please turns merged commits into a human-approved Release-PR, a Keep a Changelog entry, and a SemVer tag - and which repos use release-plz, goreleaser, or Changesets instead.
- Place a commit inside the trunk-based, protected-main branching and release flow, from feature branch to gated release.
Prerequisites
- Basic familiarity with Git commits, branches, and pull requests.
- Helpful: the AGENTS floor module, which introduces Conventional Commits as rule 2.
Units
- 01Introduction4 min
- 02Conventional Commits in depth8 min
- 03Versioning and releases8 min
- 04Knowledge check5 min
- 05Summary3 min
Related
- Design and version an API Shape a clean, consistent API against a clear API design standard - resources, standard methods, typed errors, cursor pagination, idempotency - then version and deprecate it under a versioning policy so no consumer is ever broken without consent.
- Apply the naming standards Name a new identifier, file, repo, or branch the way an AI-native org does - keyword-first, no redundant prefix, cased by role - and tell a functional keyword apart from a product codename, so your first artifact passes the naming gate by default.
- Read the pipeline that ships your change Follow a change from a pull request through the canonical CI stage set to a gated production deploy - the ordered gates a pipeline runs, why CI is the real gate, and how the deployment model promotes one signed artifact dev to staging to prod.