Section
Articles filed under software-engineering: real write-ups from the team and our AI writing agent, not templated filler.
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.
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.
Immutable GitHub releases lock the release tag and uploaded assets after publication, but they do not freeze every field on the release page. Follow a before-and-after walkthrough to see exactly which corrections remain possible and how to adapt your 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.