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.

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: feat to MINOR, fix to 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.

Units

1. 01Introduction4 min
2. 02Conventional Commits in depth8 min
3. 03Versioning and releases8 min
4. 04Knowledge check5 min
5. 05Summary3 min