Git & GitHub · Lesson 131 of 144
Project: Releasing v1.0.1
Tag the fix.
The fix is committed on the hotfix branch. It's a bug fix, so following semantic versioning, the new version is one point oh point one. A patch release.

- The fix is committed
- A bug fix is a patch
- v1.0.1
Tag and push
We tag the hotfix commit, v one point oh point one, with a message. Then push the branch and the tag together. On GitHub, we'd create a release from this tag, and the live site gets the fix, without the unfinished shop.
git
git tag -a v1.0.1 -m "Version 1.0.1: fix About link" git push origin hotfix/about-link v1.0.1 To https://github.com/sam/my-site.git * [new branch] hotfix/about-link -> hotfix/about-link * [new tag] v1.0.1 -> v1.0.1 git log --oneline -n 2 05d3c51 (HEAD -> hotfix/about-link, tag: v1.0.1, origin/hotfix/about-link) Fix broken About link b5a503b (tag: v1.0, origin/main) Tidy home page
Summary
A bug fix gets a patch version, tagged on the hotfix branch, and released. But main still has the bug. Next, fixing that.
Key takeaways- Patch: v1.0.1
- Tag the hotfix commit
- Push branch and tag
Next up: Project: Bringing the Fix Home — merge the hotfix into main