chore(release): release version 1.39.0 - #9965
Conversation
goose Release Manual Testing ChecklistVersion: 1.39.0Identify the high risk changes in this ReleaseIt will generate an analysis report in Regression TestingMake a copy of this document for each version and check off as steps are verified. Provider Testing
Starting ConversationsTest various ways to start a conversation:
RecipesCreate Recipe from Session
Use Existing Recipe
Recipe Management
Recipe from File
recipe:
title: test recipe again
description: testing recipe again
instructions: The value of test_param is {{test_param}}
prompt: What is the value of test_param?
parameters:
- key: test_param
input_type: string
requirement: required
description: Enter value for test_param
ExtensionsManual Extension Addition
Playwright Extension
Extension with Environment Variables
Speech-to-Text (Local Model)
Settings
Follow-up IssuesLink any GitHub issues filed during testing: Tested by: _____ |
macOS ARM64 Desktop App (Apple Silicon)📱 Download macOS Desktop App (arm64, unsigned) Instructions: The easiest way is to just run the following script:
script which will download the latest release (or you can specify the release you need), does the If you need to do this manually:
The signing step is only needed if you do something that uses mac entitlements like speech to text |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 5edf7e8f87
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| let (transport, mut stderr) = TokioChildProcess::builder(command) | ||
| .stderr(Stdio::piped()) | ||
| .spawn()?; |
There was a problem hiding this comment.
Restore Windows job cleanup for MCP children
When running on Windows, this spawn path is now the place creating stdio MCP extension processes, but the Windows Job Object attach was removed immediately after .spawn(). If goosed/desktop exits unexpectedly or is terminated before the async transport Drop/graceful shutdown runs, Windows leaves child processes and their descendants alive, so npx/uvx MCP servers can persist after Goose is closed. Please keep the job-object attach, or an equivalent Windows process-tree cleanup, around this spawn.
Useful? React with 👍 / 👎.
|
Release v1.39.0 has been tagged and pushed. Closing this PR (version bump was already merged to main). |
macOS ARM64 Desktop App (Apple Silicon)📱 Download macOS Desktop App (arm64, unsigned) Instructions: The easiest way is to just run the following script:
script which will download the latest release (or you can specify the release you need), does the If you need to do this manually:
The signing step is only needed if you do something that uses mac entitlements like speech to text |
Release v1.39.0
Test before Release
GITHUB_TOKEN(docs).How to Release
Push the release tag to trigger the release:
git fetch && git tag v1.39.0 origin/release/1.39.0 git push origin v1.39.0The 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.39.0branch before tagging.Important Notes
mainChanges in This Release
Comparing:
v1.38.0...v1.39.0This release PR was generated automatically.