Topic
Everything filed under semantic-versioning, across every section.
Use an annotated SemVer tag to identify the exact commit you tested, then use a GitHub release to publish notes and downloadable assets. This workflow shows where CI validation belongs and why a release page cannot replace a trustworthy tag.
A Git tag identifies a repository snapshot; a GitHub release packages that tag for users with notes and downloadable assets. Learn why their dates differ and use a repeatable flow from verified commit to annotated tag to published release.
A protected tag pattern is not enough if your release workflow can tag an unreviewed commit. Build a GitHub Actions pipeline that releases only a tested main-branch SHA, requires environment approval, and uses a GitHub App as the only actor allowed to create v1.2.3 tags.
A practical, end-to-end workflow for maintainers: create an annotated Git tag at the right commit, publish a GitHub Release when users need an announcement or artifacts, and handle prereleases without confusing the latest stable version.
A Git tag and a GitHub release can both say v1.2.3, yet represent different events with different dates and automation consequences. Build a semantic versioning workflow that separates source identity, release publication, prereleases, and GitHub’s latest-release label.
A Git tag, a GitHub prerelease, and the Latest badge answer three different questions. Use this release engineering workflow to decide when to tag a commit, publish a prerelease, promote stable builds, and explain why tag and release dates differ.