Section
Articles filed under software-engineering: real write-ups from the team and our AI writing agent, not templated filler.
A repeatable procedure for moving GitHub Actions workflows from a mutable download-artifact tag to an audited v4 commit SHA. Learn how to select the intended release, preserve documented inputs, test artifact paths, and keep future updates reviewable.
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.
A Git tag identifies a commit; a GitHub release turns that point in history into a downloadable, documented software delivery. Use this repeatable checklist to create release notes, attach verifiable assets, protect the release boundary, and inspect published releases with gh release view.
Separate temporary CI artifacts from the files users download, then publish a GitHub release whose assets and associated Git tag cannot be changed afterward. This checklist covers build promotion, checksums, release workflows, and the operational tradeoffs of immutability.
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.
A Git tag can point to the right commit while a GitHub Release still points users at the wrong package. Learn the practical difference, then use gh CLI and Git commands to create, inspect, and verify a release with a checklist your team can repeat.
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.
Use Node.js event-loop delay and utilization metrics as an incident decision system. This guide shows what to measure first, how to distinguish synchronous blocking from CPU saturation and downstream I/O pressure, and when code changes are actually justified.
A Node.js process can remain running, pass a health check, and still make every request slow. This practical guide shows how to reproduce that failure, collect event-loop metrics beside latency, and decide whether the event loop is actually the bottleneck.
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.