First Release Tag

First Release Tag

Tagging BookNest's First Release

package.json has said "version": "1.0.0" since First Repository. Sam merges the waiting dev-docs branch (Working with Remotes), tags the result as 1.0.0, and tags an older commit after the fact:

Tagging the release, and tagging an earlier commitShell

git merge -q --no-ff dev-docs -m "Merge the npm run dev documentation"
git tag -a v1.0.0 -m "BookNest 1.0.0: catalog API with search, sorting and paging"
git tag -a v0.9.0 e2b46bd -m "BookNest 0.9.0: first catalog with title search"
git show --no-patch v1.0.0

Output

tag v1.0.0
Tagger: Sam Rivera <sam@example.com>
Date:   Fri Sep 25 11:10:00 2026 +0800
BookNest 1.0.0: catalog API with search, sorting and paging
commit 8211cbb93a9e88f76e73cf3792faab3864d7ad86
...

git show prints the tag object, then the commit. The commit argument tagged e2b46bd, Branching and Merging's catalog search merge, as v0.9.0, with today's tagger date: when the release was named. Tag the exact commit you tested, with a message that says what the release contains.

MENU