Skip to content

chore(release): release version 1.45.1 (patch) - #10803

Closed
github-actions[bot] wants to merge 1 commit into
release/1.45.0from
release/1.45.1
Closed

chore(release): release version 1.45.1 (patch)#10803
github-actions[bot] wants to merge 1 commit into
release/1.45.0from
release/1.45.1

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Release v1.45.1

Test before Release

  1. Approve the workflows for this PR (scroll to bottom) to trigger CI and produce the Desktop bundle for testing.
  2. Make sure all check workflows pass.
  3. Install the Desktop bundle from the download links (posted as a comment below when it is ready).
  4. Complete the goose Release Manual Testing Checklist (posted as a comment below).

How to Release

Push the release tag to trigger the release:

git fetch && git tag v1.45.1 origin/release/1.45.1
git push origin v1.45.1

The tag push will trigger the release build. This PR will be automatically closed.

Cherry-Picks

If you need to include additional fixes, cherry-pick them into the release/1.45.1 branch before tagging.

Important Notes

  • All commits in this release should have corresponding cherry-picks in main
  • This PR can be closed if the release is not needed.

Changes in This Release

Comparing: v1.45.0...v1.45.1

  • chore(release): release version 1.45.1 (215fb5b)

This release PR was generated automatically.

@github-actions

Copy link
Copy Markdown
Contributor Author

goose Release Manual Testing Checklist

Download the release builds from this PR. Once a build is ready, the actions bot will post a comment on this PR
with instructions on how to download and sign.

Use the following script to create a risk assessment and testing plan:

./workflow_recipes/release_risk_check/run.sh 1.45.1

It will generate an analysis report in /tmp/release_report_final.md and perform testing is necessary for high risk pr changes.

Run the goose self-test recipe

goose run --recipe goose-self-test.yaml

Have goose produce a test plan

Open the release candidate desktop app and have goose produce a test plan by pointing it at this PR. Use a prompt like

Look at the notes in PR and the report at /tmp/release_report_final.md and investigate potential risks in this release. After familiarizing yourself with the scope of each change, produce a suggested test plan that I should follow before publishing the release.

goose will produce a plan. Follow this plan to finish testing.

@alexhancock alexhancock self-assigned this Jul 30, 2026
@jamadeo jamadeo closed this Aug 12, 2026
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.

2 participants