Topic
Everything filed under devops, across every section.
Git’s newest tag can mean the greatest version or the most recent tag-related date—and those can point to different releases. Use this decision guide and a stable-tag filter to choose the right one for your script.
Protected tags stop an unauthorized or accidental Git ref change before release publication. GitHub immutable releases lock the tag and release assets after publication; use this lifecycle-based guide to decide when you need one, the other, or both.
GitHub’s legacy tag protections were migrated to tag rulesets in August 2024. Use this post-migration checklist to inventory tag-targeting rulesets, verify release-tag writers and bypass actors, clean up retired API tooling, and rehearse safe tag-creation failures.
Immutable GitHub releases remove the usual escape hatch: after publication, you cannot add, replace, or delete assets, and the release tag is locked. Build a draft-first pipeline that produces, verifies, uploads, and checks every artifact before the one irreversible publish step.
GitHub tag rulesets and immutable releases solve different points in a production release workflow. Use tag rulesets to control who can create, update, or delete release tags before publication, and immutable releases to preserve the published tag and assets afterward.
GitHub immutable releases protect published tags and assets, but they also remove your easiest recovery options. Use this pre-publication checklist to verify the commit, binary, checksums, release metadata, and rollback path before publication.
Migrate legacy GitHub protected-tag patterns to tag-targeting repository rulesets without accidentally widening release permissions. Includes a translation checklist, an overlap example, and a validation plan for release automation.
GitHub’s legacy tag protection sunset is not just a settings migration. Use this practical checklist to inventory release tags, verify migrated tag rulesets, test controls in a low-risk repository, and assign long-term ownership.
A release tag is a dependency contract, not a label your team can casually move. Learn how GitHub tag-targeting rulesets prevent tag rewrites, where GitHub Releases fit, and how to scope an immutable-tag policy without blocking legitimate development tags.
Use the GitHub Changelog as your source of record and a release-notes aggregator as an early-warning layer. This workflow shows how to triage Copilot, Actions, security, CLI, and Enterprise updates into ignore, review, test, or act-now decisions.