From e483d9907a847a1e399640a235821447faf61c67 Mon Sep 17 00:00:00 2001 From: Michael Neale Date: Mon, 19 Jan 2026 14:10:54 +1100 Subject: [PATCH 1/4] tweak release docs Thought could use some high level explanation as was slightly confused. --- RELEASE.md | 18 ++++++++++++++++-- 1 file changed, 16 insertions(+), 2 deletions(-) diff --git a/RELEASE.md b/RELEASE.md index 671f60f5826e..ae2a0ddd972d 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -1,15 +1,29 @@ # Making a Release -You'll generally create one of two release types: a regular feature release (minor version bump) or a bug-fixing patch release (patch version bump). Regular releases start on main, while patch releases start with an existing release tag. goose uses GitHub actions to automate the creation of release branches. The actual releases are triggered by tags. +You'll generally create one of two release types: a regular feature release (minor version bump like 1.20) or a bug-fixing patch release (patch version bump like 1.20.1). + +Regular releases start on main, while patch releases start with an existing release tag. goose uses GitHub actions to automate the creation of release branches. The actual releases are triggered by tags. +With bug fixing releases you will be cherry picking fixes to that branch, testing, and then releasing from that. ## Minor version releases -These are typically done once per week. There is an [action](https://github.com/block/goose/actions/workflows/minor-release.yaml) that cuts the branch every Tuesday, but it can also be triggered manually. Commits from main can be cherry-picked into this branch. +These are typically done once per week. There is an [action](https://github.com/block/goose/actions/workflows/minor-release.yaml) that cuts the branch every Tuesday, but it can also be triggered manually. Commits from main can be cherry-picked into this branch as needed before release. To trigger the release, find [the corresponding PR](https://github.com/block/goose/pulls?q=is%3Apr+%22chore%28release%29%22+%22%28minor%29%22+author%3Aapp%2Fgithub-actions+) and follow the instructions in the PR description. ## Patch version releases Minor and patch releases both trigger the creation of a branch for a follow-on patch release. These branches can be used to create patch releases, or can be safely ignored/closed. +You can cherry pick fixes into this branch. To trigger the release, find [the corresponding PR](https://github.com/block/goose/pulls?q=is%3Apr+%22chore%28release%29%22+%22%28patch%29%22+author%3Aapp%2Fgithub-actions+) and follow the instructions in the PR description. + + +## high level release flow: + +* check out and cherry pick (if needed) changes to the branch you are going to release (eg the patch branch) +* Test locally if you can (just run-ui) +* Push changes to that branch, wait for build +* Download and test the .zip from the release PR +* If happy, follow the instructions on the release PR to tag and release (tagging will trigger the real release from there) + From 5039748c590c83324133ea67cf746cc6ff273daf Mon Sep 17 00:00:00 2001 From: Michael Neale Date: Mon, 19 Jan 2026 16:13:43 +1100 Subject: [PATCH 2/4] Update RELEASE.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- RELEASE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/RELEASE.md b/RELEASE.md index ae2a0ddd972d..fab17c7185ba 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -19,7 +19,7 @@ You can cherry pick fixes into this branch. To trigger the release, find [the corresponding PR](https://github.com/block/goose/pulls?q=is%3Apr+%22chore%28release%29%22+%22%28patch%29%22+author%3Aapp%2Fgithub-actions+) and follow the instructions in the PR description. -## high level release flow: +## High level release flow: * check out and cherry pick (if needed) changes to the branch you are going to release (eg the patch branch) * Test locally if you can (just run-ui) From 7cf8de715bf2c29b87b492b925d7013aca77f83d Mon Sep 17 00:00:00 2001 From: Michael Neale Date: Thu, 22 Jan 2026 08:58:18 +1100 Subject: [PATCH 3/4] Apply suggestions from code review Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- RELEASE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/RELEASE.md b/RELEASE.md index fab17c7185ba..396055e3ec9d 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -3,7 +3,7 @@ You'll generally create one of two release types: a regular feature release (minor version bump like 1.20) or a bug-fixing patch release (patch version bump like 1.20.1). Regular releases start on main, while patch releases start with an existing release tag. goose uses GitHub actions to automate the creation of release branches. The actual releases are triggered by tags. -With bug fixing releases you will be cherry picking fixes to that branch, testing, and then releasing from that. +For bug-fixing releases, you will cherry-pick fixes into that branch, test, and then release from it. ## Minor version releases From 0fe56693f99a21b333a26b74a78b8a1ed018e9a9 Mon Sep 17 00:00:00 2001 From: Michael Neale Date: Thu, 22 Jan 2026 09:05:55 +1100 Subject: [PATCH 4/4] Apply suggestions from code review Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- RELEASE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/RELEASE.md b/RELEASE.md index 396055e3ec9d..881ca6d290c5 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -21,7 +21,7 @@ To trigger the release, find [the corresponding PR](https://github.com/block/goo ## High level release flow: -* check out and cherry pick (if needed) changes to the branch you are going to release (eg the patch branch) +* check out and cherry-pick (if needed) changes to the branch you are going to release (eg the patch branch) * Test locally if you can (just run-ui) * Push changes to that branch, wait for build * Download and test the .zip from the release PR