Update release testing instructions - #10122
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: a784e464ff
ℹ️ 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".
| - type: builtin | ||
| name: summon | ||
| - type: builtin | ||
| name: extensionmanager |
There was a problem hiding this comment.
Adding extensionmanager here does not provide the platform__search_available_extensions tool that Phase 2 asks for; the extension manager's tools are prefixed with the normalized extension name (extensionmanager__search_available_extensions, as covered by crates/goose/tests/agent.rs). When the release self-test runs all phases, the extension-system step will fail before it can discover or toggle extensions.
Useful? React with 👍 / 👎.
| - type: builtin | ||
| name: todo | ||
| - type: builtin | ||
| name: summon |
There was a problem hiding this comment.
Adding only summon makes the Phase 3 load/delegate steps reachable, but the built-in skill check below still calls load(source: "goose-doc-guide"). Summon's load discovers recipes, agents, and subrecipes, while built-in skills are served by the separate skills extension through load_skill, so the all-phases release self-test will report a false failure even when skill loading is working.
Useful? React with 👍 / 👎.
* main: fix: tolerate partial Responses output items (#10108) fix(databricks): always use OpenAI-compatible "parameters" for tools (#10101) fix(providers): unescape shell-escaped image paths (#10098) chore(deps-dev): bump js-yaml from 4.1.1 to 4.2.0 in /documentation (#10107) regenerate schema (#10166) chore(deps): bump actions/stale from 10.1.1 to 10.3.0 (#10050) chore(deps): bump actions/attest-build-provenance from 4.1.0 to 4.1.1 (#10049) chore(deps): bump pnpm/action-setup from 6.0.8 to 6.0.9 (#9892) Update EmpirioLabs provider display name to EmpirioLabs AI (#10126) add declarative provider support to goose-providers crate (#9992) fix(desktop): seed mac auto-update config (#10132) Update release testing instructions (#10122)
2 participants
Replaces the old release log with instructions on how to produce a release plan.
We can also produce the plan as part of the automation, but I find doing it manually is a nice first sanity check of the release candidate anyway.