Search
Results for “automation”
- software-engineering
GitHub Releases vs Git Tags: A Practical Checklist for Automated Publishing
A Git tag, a GitHub release record, and a release asset are three different things with different timestamps and failure modes. Use this checklist and pipeline example to publish reproducible releases without accidentally rebuilding, retagging, or distributing the wrong binary.
- developer-tools
A GitHub Actions Release Workflow That Automates Drafts and Assets Without Bypassing Human Release Decisions
Build release artifacts, changelogs, checksums, and draft releases automatically while keeping version approval, final release-note review, publishing, and rollback decisions with people. This reference design uses protected branches, immutable tags, GitHub Environments, and an idempotent draft policy.
- software-engineering
Migrate download-artifact v3 to v4 and Verify Deploy Directory Layouts
A practical GitHub Actions migration guide for replacing actions/download-artifact@v3 with v4 without silently changing what your deploy job publishes. Map common download patterns, update artifact producers, and add layout checks to a build-test-deploy pipeline.
- software-engineering
9-Step 2026 Checklist for Validating GitHub Tag Rulesets After Legacy Tag Protections
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.
- software-engineering
How to Publish Immutable GitHub Releases Without Discovering Missing Assets Too Late
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.
- software-engineering
Immutable GitHub Releases: What You Still Can—and Cannot—Edit After Publishing
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.
- software-engineering
Build a Safer GitHub Release Pipeline with Protected Tags, Release Assets, and Least-Privilege Tokens
Create GitHub Releases only from controlled version tags, keep build jobs read-only, and give release publishing a short-lived contents: write token. Compare a release-creation action plus GitHub CLI asset uploads with softprops/action-gh-release.
- technology
Migrate download-artifact to v4: Test Paths, Compatibility, and Deploy Contracts
A practical before-and-after migration for GitHub Actions artifact workflows. Learn how v4 changes artifact compatibility, availability, and download directories—and add checks that catch broken deploy paths before production.
- software-engineering
Migrate GitHub Protected Release Tags to Rulesets: An Evergreen Checklist
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.
- software-engineering
How to Design a GitHub Ruleset Policy for Release Tags and CI
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.
- software-engineering
7 Steps to Replace GitHub Protected Tags with Repository Rulesets Safely
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.
- software-engineering
GitHub Protected Tags Migration: A Release Pipeline and Deployment Checklist
Migrate legacy GitHub tag protections without breaking release automation or accidentally bypassing production environment controls. This playbook inventories tag dependencies, separates tag authorization from deployment authorization, and tests the cutover safely.
- software-engineering
Stop Treating Git Tags, GitHub Releases, and CI Artifacts as the Same Release Output
A Git tag identifies source, a GitHub release communicates a supported version, and a CI artifact moves build outputs through automation. Map each output to its consumer and retention policy, then use this handoff checklist to prevent broken downloads and unreproducible releases.
- software-engineering
How to Choose Immutable Tags or Commit SHA Pins for GitHub Actions
A practical comparison of mutable tags, immutable release references, and full commit-SHA pins for GitHub Actions. Use actions/download-artifact to choose a policy that balances supply-chain security, readable reviews, automated updates, and fast rollback.
- software-engineering
Git Tags vs GitHub Releases in 2026: A Reliable SemVer Workflow
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.