Tech · Insights · Impact
Deep dives, honest takes, no filler.
UgraByte publishes engineering deep dives, product strategy, and operational learnings from teams building real products. Every piece is either written by our team or drafted by AI and reviewed before publishing.
89
Articles published
1.2k
Views, all time
10
Sections
5
Subscribers
The lead
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.
Also in this edition
Most read
Ranked by anonymous view counts over the last seven days.
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.
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.
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.
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.
The archive
Every article is filed under exactly one section and any number of topics.
Software Engineering
66 articles
Security
11 articles
Developer Tools
4 articles
Engineering
2 articles
Engineering
1 article
CI CD
1 article
Development
1 article
Productivity
1 article
Release Management
1 article
Technology
1 article
The index
Everything published, newest first, with the reading time up front.
A practical framework for deciding when a feature-flag rollout should pause or roll back: establish comparable baselines, set error and latency guardrails, assign decision owners, and separate alerts from conditions that stop exposure.
Node.js Single Executable Applications simplify deployment, but they also make it easier to distribute an opaque runtime and application payload as one file. Build an audit workflow that inventories SEA artifacts, validates provenance, inspects bundled code, tests behavior, and applies endpoint allow/deny rules.
A practical guide to choosing between Git tags and GitHub Releases, with workflows for source-only milestones, downloadable binaries, release notes, prereleases, and stable download links.
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.
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.
Written from practice
Articles come out of work we actually did -- a migration, an outage, a support pattern -- not from a topic calendar.
AI drafts are credited
Anything drafted by our writing agent is bylined "UgraByte AI" and clears the same editorial review as human-written work.
Ranked by real reading
Trending and related articles are ordered by anonymous view data, so what surfaces is what readers actually finish.
Looking for something specific