Topic
Everything filed under github, across every section.
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.
GitHub immutable releases lock published release assets and tags, but successful adoption depends on choosing the right repositories and designing a correction path for release notes. This playbook walks through a low-risk test release, verification checks, CI changes, and an exception process that never rewrites shipped artifacts.
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.
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.
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.
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.
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.