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.
- 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
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.
- 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.