DevOps · Cluster
Release Engineering
Versioning, changelogs, and branching.
- 01 Semantic Versioning as a Compatibility Contract What each of the three version numbers is allowed to promise, how the ordering rules work, and why the compatible-change rule only holds for the parts of a surface a project actually constrains.
- 02 Deriving a Changelog from Commit Messages How a structured commit header turns release notes into a mechanical transformation, which parts of the convention are load-bearing, and where the encoder and the reader disagree.
- 03 Lockfiles and How a Version Range Becomes a Tree Why a range in a manifest is not a pin, what a lockfile records that the manifest cannot, and how resolvers settle or fail on conflicting requirements.
- 04 Release Trains, Cut Points, and Hotfix Branches How a release branch is cut from a moving mainline, what the cut point guarantees, and how a hotfix reaches both the released line and the mainline without duplicating the change.
- 05 Pre-release Channels and Promotion in Package Registries How candidate builds are published under pre-release identifiers, how dist-tags and channels make the same version resolve differently for different consumers, and why promotion should never rebuild.
- 06 Fixed and Independent Versioning in a Monorepo How a repository containing many packages decides whether they share one version or several, what the coupling does to upgrades, and how change detection assigns a bump to each package.
- 07 Describing Breaking Changes So Consumers Can Act on Them Why a one-line note that an API changed forces every consumer to read the diff, and the shape of an entry that names the affected surface, the failure it produces, and its replacement.
- 08 Immutable Artifact Coordinates and Why Digests Matter How a version-plus-repository name identifies a byte string, what breaks when the mapping can change, and how attestations bind a build input set to the digest that was published.
- 09 Release Gates: Verifying the Cut Before It Ships What a release gate can mechanically check, why reproducibility is the only claim about a build that a second machine can settle, and how a gate fails without becoming a step people bypass.
- 10 Deprecation Windows and the Machinery Behind Compatibility Shims How an old interface is kept working while its replacement is adopted, what a shim must translate, and how to decide when removal is safe rather than merely scheduled.