Topic
Everything filed under release-engineering, across every section.
GitHub immutable releases prevent published release tags and assets from being changed, but they do not govern who may create a tag in the first place. Use this migration checklist to pair immutable releases with tag rulesets, CI identities, and a tested release workflow.
Turn an inherited protected-tag setup into an explicit release policy: decide who may create, move, or delete version tags, then test the policy with the same identity your release automation uses.
Use a pre-publish gate to catch release mistakes before GitHub locks assets and tags, then follow a practical recovery path for bad binaries, wrong commits, incorrect notes, and accidental latest releases.
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 tag rulesets stop unauthorized tags from being created, moved, or deleted before release publication. Immutable releases protect the tag and downloadable assets after publication; use both for v1.* production releases.
A moved v2.4.0 tag can make the same download URL point to different source code, while an editable release can replace the binary users already trusted. This guide separates Git tags, GitHub releases, tag rulesets, and immutable releases, then builds a practical workflow for locking versioned software.
A GitHub release, its underlying Git tag, and a tag ruleset protect different parts of a software delivery process. This guide walks through a signed-version workflow, shows where immutable releases fit, and provides a decision table for selecting the right controls.
Replace retired GitHub protected-tag rules without accidentally allowing release tags to be moved, deleted, or recreated. This walkthrough maps common legacy policies to tag-targeting rulesets, fnmatch patterns, bypass choices, and practical verification steps.
Replace retired GitHub tag protection rules with tag rulesets without accidentally blocking release automation. This checklist covers pattern inventory, fnmatch scope, safe testing, automation bypasses, and release-policy documentation.
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.