Library › Book 17 › Tagging and Releases -- Marking History, Managing Versions
Tagging and Releases -- Marking History, Managing Versions
6.1🔒Why Tags MatterTags mark specific points in Git history -- typically releases. They create an audit trail: which commit was released, what was tested, and…
6.2🔒Creating TagsA lightweight tag is just a pointer to a commit. It has no additional metadata -- no author, no date, no message.
6.3🔒Working with TagsCommon Mistake: Checking out a tag and making commits in detached HEAD state. Any commits you make will be orphaned when you switch…
6.4🔒Semantic Versioning (SemVer)Most projects use semantic versioning: MAJOR.MINOR.PATCH
6.5🔒Associating Test Results with ReleasesThe gold standard is a release process where test results are permanently linked to the release tag.
6.6🔒Release WorkflowA typical release workflow:
6.7🔒Comparing ReleasesGit makes it easy to see what changed between releases -- essential for writing test plans and identifying what needs regression testing.
6.8🔒Interactive Exercise: Release Tagging Workflow
6.9🔒Exercises1. Create an annotated tag for a "release" with test result metadata in the message. 2. List all tags in your project. Show the details of…
6.10🔒Career Translation- Designed and implemented release tagging workflow with annotated tags containing test result metadata, browser coverage, and CI run…
6.11🔒Q&AInterview Depth CheckPrompt: A customer reports a critical bug on version 2.3.1 of your application. The current production version is 2.5.0. How do you use Git…