Skip to content
Module
Module 6 of 6Lesson 2 of 3~12 min

Tags, versions and release notes

Without a clear version number or readable notes, users and support teams lose track of what changed. This lesson teaches you to pick the next number with semantic versioning, understand how a release is marked in the repository and write release notes that speak to users.

Take this lesson: your first course is freeSee the full syllabus

Lesson objective

By the end of this lesson, you will be able to work out the next version number under semantic versioning from the merged changes, know how a tag is created and published, and write release notes that help users.

Topics covered

  • semantic versioning
  • Git tags
  • release notes
  • changelog
  • releases

Where it fits

Coding agent, releases and end-to-end delivery

How do I bring an AI agent into this workflow, mark a release and ship my first improvement?

Lessons in this module

  1. Put an AI coding agent to work in a team repository
  2. Tags, versions and release notes (this lesson)
  3. Final workshop: ship an improvement end to end

What you will learn in this module

This lesson is part of the course Git for PMs: ship as a team without putting production at risk

  • Work on a short-lived branch with everyday Git commands (or their GitHub equivalents), small commits named by convention, and stay in sync with main.
  • Open a small, well-described pull request, get the right review, pass the required checks, validate the preview and choose the merge method.
  • Choose the right way to undo a change (restore, revert, reset, deployment rollback) depending on whether it is local, pushed, merged or already in production.
  • Keep an AI coding agent under control in a team repository (dedicated branch, written rules, protected secrets, proof of verification, human review before merge).
  • Tie merged changes to a release (tag, semantic versioning, changelog) and write release notes that help users.

Related courses