Skip to content

Write down how to cut a release - #2

Merged
paulglover merged 1 commit into
mainfrom
release-checklist
Aug 10, 2026
Merged

Write down how to cut a release#2
paulglover merged 1 commit into
mainfrom
release-checklist

Conversation

@paulglover

Copy link
Copy Markdown
Owner

A release checklist in the README, between "Working on it" and "License".

The two things worth writing down are the ones that are only obvious after getting them wrong:

  • The tag comes first. make deb takes its version from git describe, so a build from an untagged or dirty tree names the package after the previous release.
  • make deb alone is amd64 only. v0.1.0 shipped arm64 as well; nothing in the repo recorded that, so the next release would have quietly dropped it.

🤖 Generated with Claude Code

https://claude.ai/code/session_01T4oAqvh4CPXFK2uWJnSXpa

Two things that are only obvious once you have got them wrong: the tag has to
come first, because `make deb` reads the version out of `git describe` and a
build from an untagged or dirty tree names itself after the previous release;
and `make deb` on its own is amd64 only, which quietly ships a release that a
Pi cannot install.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01T4oAqvh4CPXFK2uWJnSXpa
@paulglover
paulglover merged commit c32c924 into main Aug 10, 2026
1 check passed
@paulglover
paulglover deleted the release-checklist branch August 10, 2026 21:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant