From 0789e1a59f3cd3d975f960f21e2bef30c87124d8 Mon Sep 17 00:00:00 2001 From: dave3d <611581+dave3d@users.noreply.github.com> Date: Wed, 18 Nov 2026 15:54:18 +0000 Subject: [PATCH 1/2] Initial plan From d40bf2f4db2c171b77ce33f6adef84ea92e7109f Mon Sep 17 00:00:00 2001 From: dave3d <611581+dave3d@users.noreply.github.com> Date: Wed, 18 Nov 2026 15:55:38 +0000 Subject: [PATCH 2/2] Document consistent release tagging Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> --- ReleaseNotes.md | 15 +++++++++++---- 1 file changed, 11 insertions(+), 4 deletions(-) diff --git a/ReleaseNotes.md b/ReleaseNotes.md index c1f5908..df54069 100644 --- a/ReleaseNotes.md +++ b/ReleaseNotes.md @@ -1,7 +1,14 @@ -# Dave's Release Notes +# Release Process -Use Github's release mechanism to create a new release. -Do not do it from the command line. Use the web interface. +Create an annotated tag for the release, then push it to the repository. For +example: -Dave is dumb. Do not be Dave. +```sh +git tag -a v0.4.5 -m "Release v0.4.5" +git push upstream v0.4.5 +``` + +Replace `upstream` with the name of the remote you push releases to. Pushing a +`v*` tag triggers the publish workflow, which creates a GitHub release titled +`Release v0.4.5` and generates its release notes.