Search
Results for “backend-engineering”
- software-engineering
9-Step Rollback-Ready Release Checklist for Small Engineering Teams
Turn release management into a repeatable, executable checklist with test evidence, named approvers, deployment ownership, measurable rollback triggers, and post-release verification.
- software-engineering
How to Investigate Node.js Latency With Event-Loop Metrics, Not CPU Alone
Learn to distinguish a blocked Node.js event loop from slow downstream I/O using event-loop delay, event-loop utilization, request timing, and CPU measurements. Includes instrumentation code, a diagnosis matrix, and concrete remediation decisions.
- software-engineering
GitHub Releases vs Git Tags: A Practical Workflow for Prereleases and Latest Releases
A Git tag, a GitHub prerelease, and the Latest badge answer three different questions. Use this release engineering workflow to decide when to tag a commit, publish a prerelease, promote stable builds, and explain why tag and release dates differ.
- 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
Stop Rewriting Releases: A Staged Playbook for GitHub Immutable Releases
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.
- software-engineering
Annotated Git Tags vs GitHub Releases: A Practical Versioned Delivery Workflow
Use an annotated SemVer tag to identify the exact commit you tested, then use a GitHub release to publish notes and downloadable assets. This workflow shows where CI validation belongs and why a release page cannot replace a trustworthy tag.
- software-engineering
Migrate GitHub Protected Tags to Rulesets: Checklist, API Replacement, and Tag Target Verification
GitHub’s legacy tag-protection rules were migrated to tag rulesets after scheduled API brownouts in 2024. Use this checklist to translate patterns and permissions, create or audit repository rulesets through the supported path, and verify that release tags still point to the intended commits.
- 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
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
Stop Accidental Releases: Protect v1.2.3 Tags and Release Only Approved GitHub Actions Builds
A protected tag pattern is not enough if your release workflow can tag an unreviewed commit. Build a GitHub Actions pipeline that releases only a tested main-branch SHA, requires environment approval, and uses a GitHub App as the only actor allowed to create v1.2.3 tags.
- software-engineering
Signed Git Tag Verification: Check the Signature and the Commit Before Publishing
A valid signature is only one part of release provenance. Verify the annotated tag, authorize its signer by fingerprint, compare its target with an independently approved commit, and build from that commit.
- software-engineering
GitHub Immutable Tag Rulesets: Stop v1.2.0 Rewrites and Accidental Retagging
A release tag is a dependency contract, not a label your team can casually move. Learn how GitHub tag-targeting rulesets prevent tag rewrites, where GitHub Releases fit, and how to scope an immutable-tag policy without blocking legitimate development tags.
- 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
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
Build Once, Publish GitHub Release Assets, and Verify the Download in GitHub Actions
Turn a tagged build into a reproducible GitHub Release: upload one immutable build bundle as a workflow artifact, attach that exact bundle to the release, then download and checksum the published asset as a consumer would.
- software-engineering
GitHub Protected Tag Migration in 2026: Translate Tag Policies into Rulesets
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.
- software-engineering
GitHub Protected Tags vs Immutable Releases in 2026: Which Release Control Fits Your Workflow?
Protected tags stop an unauthorized or accidental Git ref change before release publication. GitHub immutable releases lock the tag and release assets after publication; use this lifecycle-based guide to decide when you need one, the other, or both.
- software-engineering
A Pre-Launch GenAI Risk Checklist for Internal Chatbots and Developer Tools
Turn NIST’s generative AI risk guidance into a practical release gate for a coding assistant, repository chatbot, or internal support bot. Use this checklist to test data exposure, harmful outputs, human review, evaluation coverage, and incident response before enabling real users.
- software-engineering
GitHub Protected Tags vs Immutable Releases: How to Design a Release Process That Protects Both
A protected tag can stop a version name from being moved, while an immutable release protects the published package and its associated tag after publication. Learn where each control begins and ends, and how to combine them in a practical GitHub release workflow.
- software-engineering
How to Lock GitHub Releases Safely: Tags, Rulesets, and Immutable 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.
- software-engineering
GitHub Immutable Releases vs Tag Rulesets: A Secure v1.* Release Configuration
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.
- software-engineering
Protected Tags Are Not a Published-Artifact Guarantee for Production Releases
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.
- software-engineering
GitHub Release Hotfix Playbook: 5 Decisions When an Immutable Tag or Asset Is Wrong
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.
- software-engineering
GitHub Protected Tags in 2026: An Audit and Migration Checklist After the Sunset
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.
- software-engineering
How to Pass Build Outputs Between GitHub Actions Jobs with upload-artifact v4
Build a reliable four-job GitHub Actions pipeline using v4 artifacts, artifact IDs, checksum verification, and a separate release-publishing step. Learn why workflow artifacts are not the same thing as GitHub Release assets.
- 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
GitHub Tag Rulesets vs Accidental Go Releases: A Practical Protection Policy
A tag named v1.8.0 can become a Go module version the moment it reaches your repository, even if nobody intended to publish a release. Build GitHub tag rulesets around Go’s version-discovery behavior, with separate permissions and workflows for prereleases and stable releases.
- software-engineering
Don’t Replace Protected Tags With Immutable Releases Alone: A 9-Step GitHub Migration
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.
- software-engineering
GitHub Changelog Triage: A Weekly Workflow for Releases, Improvements, and Retirements
Turn GitHub product changes into a 30-minute weekly operating process. Learn how to subscribe, classify releases, improvements, and retirements, assign accountable owners, run proportionate tests, and preserve decisions in a searchable log.
- software-engineering
How to Protect Git Tag Production Deployments in GitHub Actions with Rulesets and Environments
GitHub tag rulesets and environment protection solve different deployment risks. This worked production flow uses both: only release managers can create immutable version tags, and only approved tags can request access to the production environment.