Versioning as Code: Implementing Testable Release Strategies

Versioning as Code: A Testable, Fail-Fast Strategy for Enterprise Releases

Zied Hamdi introduces a DevDevOps strategy that replaces opaque YAML shell scripts with testable TypeScript logic for release management. This architecture uses package.json as the single source of truth to automate git tagging and branching with millisecond-fast local unit tests.

Why This Matters

Traditional release pipelines rely on untestable shell scripts embedded within YAML files, creating a push-and-pray environment that obscures logic from the development team. Moving this logic into the application language allows for millisecond-fast local testing and a Defense in Depth strategy, ensuring that release errors like negative version bumps are caught at the developer’s machine before reaching the CI server.

Key Insights

• Logic shouldn’t live in YAML: Shell commands inside GitHub Actions cannot be unit tested, often requiring 3-minute runner waits to verify simple script changes (Hamdi, 2026).
• Mockable Infrastructure: By wrapping native interactions like fs.readFileSync in a versionHelpers object, developers can simulate Git history to test release logic without touching a repository.
• Semantic Safety Pre-checks: Using a SEMVER_REGEX allows teams to implement semantic comparison logic that detects and forbids version downgrades or negative bumps.
• Defense in Depth: A two-tier validation system combines local Git pre-push hooks for immediate feedback with GitHub Actions auditors as a final safety release valve.
• Frictionless Local Delivery: Validating versions locally enables teams in air-gapped environments to build and package 2GB Docker artifacts without relying on cloud CI builders.

Working Examples

Testable version check logic using TypeScript instead of shell pipes.

export const versionHelpers = { getCurrentVersion: () => JSON.parse(fs.readFileSync('./package.json', 'utf8')).version, getPreviousVersion: () => JSON.parse(execSync('git show HEAD~1:package.json', { encoding: 'utf8' })).version }; export function checkVersion() { const newV = versionHelpers.getCurrentVersion(); const oldV = versionHelpers.getPreviousVersion(); const comparison = compareSemver(newV, oldV); if (comparison === 1) { return { bumped: true, version: newV }; } return { bumped: false }; }

Local Git pre-push hook to enforce versioning standards before the code leaves the developer machine.

#!/bin/bash echo 'Running pre-push validation...' npx tsx scripts/release/check-version.ts if [ $? -ne 0 ]; then echo 'Version validation failed! Push aborted.' exit 1 fi echo 'All checks passed.' exit 0

Practical Applications

• Use Case: Consultants in air-gapped enterprise environments use local package.json validation to trigger local bundle scripts for Docker image handover. Pitfall: Relying on cloud CI for metadata validation, which blocks offline builds and requires high-bandwidth downloads of large artifacts.
• Use Case: Distributed software teams use setup-hooks.sh to automate the installation of local safety valves during onboarding. Pitfall: Manual Git configuration leading to inconsistent release tagging and versioning conflicts across different developer environments.

References:

• https://dev.to/zhamdi/versioning-as-code-a-testable-fail-fast-strategy-for-enterprise-releases-1gej