updates: release 0.19.0 of the tui/sdk/etc#8806
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: 02852a63cc
ℹ️ About Codex in GitHub
Codex has been enabled to automatically 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 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| { | ||
| "name": "@aaif/goose-sdk", | ||
| "version": "0.18.0", | ||
| "version": "0.19.0", |
There was a problem hiding this comment.
This release commit is for 0.18.0, and the binary package manifests were bumped to 0.18.0, but this line moves @aaif/goose-sdk to 0.19.0 (with the same bump in ui/text/package.json). Because the npm publish workflow reads each package version directly from package.json, this creates a mixed release where SDK/TUI publish as 0.19.0 while the bundled binary packages remain 0.18.0, producing inconsistent artifacts for the same release cycle.
Useful? React with 👍 / 👎.
alexhancock
force-pushed
the
alexhancock/pnpm-workspace-update
branch
from
02852a6 to
ce26052
Compare
alexhancock
changed the title
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ce26052d69
ℹ️ About Codex in GitHub
Codex has been enabled to automatically 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 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| { | ||
| "name": "@aaif/goose", | ||
| "version": "0.18.0", | ||
| "version": "0.19.0", |
There was a problem hiding this comment.
Updating @aaif/goose to 0.19.0 here while ui/sdk/package.json stays at 0.18.0 introduces a split npm release: the publish workflow (.github/workflows/publish-npm.yml) reads each package’s own package.json version and skips already-published versions via npm view, so @aaif/goose-sdk@0.18.0 can be skipped while @aaif/goose@0.19.0 is published. That leaves the new CLI package tied to the previous SDK/binary resolution path instead of a coherent 0.19.x release set.
Useful? React with 👍 / 👎.
alexhancock
force-pushed
the
alexhancock/pnpm-workspace-update
branch
from
ce26052 to
d8f0f2e
Compare
* main: (29 commits) chore(deps): bump winreg from 0.55.0 to 0.56.0 (#8829) Fix grammar issue (#8669) colorize context window indicator (#8851) Refresh canonical model metadata from models.dev (#8838) fix(ci): prevent flaky smoke test timeouts from failing the build (#8837) updates: release 0.19.0 of the tui/sdk/etc (#8806) add a goose2 signed release flow (#8728) Port provider tests to typescript (#8237) refactor: make ACP server smaller (#8787) Add NVIDIA provider, and improve declarative provider UX (#8798) fix: removed failed provider test for deprecated providers (#8801) fix: only call cleanup when the pr is from same repo (#8799) chore: check stale for draft pr (#8803) fix: use _meta instead of meta in newSession request (#8796) fix: add missing underscore prefix in updateWorkingDir method name (#8743) feat: migrate session metadata storage from frontend overlay to backend (#8769) Add more info to BUILDING_LINUX (#8789) feat(acp): Align to new request patterns of ACP Streamable HTTP/WS transport (#8605) Dedupe and organize skills/sources (#8731) docs: add skills slash command (#8783) ...
2 participants
Summary
Bump all the versions in the pnpm workspace
Testing
N/A - No logic changes just a version bump
Related Issues
N/A
Screenshots/Demos (for UX changes)
N/A