Skip to content

RELEASING.md

Latest commit

 

History

History
62 lines (42 loc) · 1.56 KB

RELEASING.md

File metadata and controls

62 lines (42 loc) · 1.56 KB
Raw

Releasing

NullBoiler uses CalVer with the format YYYY.M.D (for example, v2026.5.29).

Pushing a tag matching v* triggers the Release workflow, which calls the shared nullclaw/nullbuilder Zig release workflow for binary artifacts. The same workflow also publishes Docker images through the repository release pipeline.

Steps

  1. Checkout and update main

    git checkout main
git pull origin main

  2. Create a release branch

    git checkout -b release/vYYYY.M.D

  3. Bump the version in build.zig.zon

    Update the .version field to match today's date:

    - .version = "2026.3.2",
+ .version = "2026.5.29",

  4. Commit the version bump

    git add build.zig.zon
git commit -m "vYYYY.M.D"

  5. Push the branch and create a PR

    git push origin release/vYYYY.M.D
gh pr create --title "vYYYY.M.D" --body "Version bump for vYYYY.M.D release."

  6. Merge the PR or get it reviewed and merged.

  7. Tag the release on main

    git checkout main
git pull origin main
git tag vYYYY.M.D
git push origin vYYYY.M.D

    The tag push triggers the release build and release Docker publishing.

Notes

  • Pull requests to main run the CI workflow through nullclaw/nullbuilder.
  • A manual release workflow dispatch requires an existing release tag, for example v2026.5.29.
  • If multiple releases happen on the same day, append a patch number, for example v2026.5.29.1.