chore: manually update version #6166
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
There was a problem hiding this comment.
Pull request overview
This PR manually updates the version number from 1.16.0 to 1.17.0 across the Rust workspace, necessitated by merge conflicts in the automated version bump PR #6131.
Key changes:
- Update workspace version from 1.16.0 to 1.17.0 in Cargo.toml
- Propagate version change to all 6 workspace packages in Cargo.lock (goose, goose-bench, goose-cli, goose-mcp, goose-server, goose-test)
Reviewed changes
Copilot reviewed 1 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| Cargo.toml | Updates the workspace package version from 1.16.0 to 1.17.0 |
| Cargo.lock | Updates version to 1.17.0 for all 6 workspace packages (goose, goose-bench, goose-cli, goose-mcp, goose-server, goose-test) |
| [workspace.package] | ||
| edition = "2021" | ||
| version = "1.16.0" | ||
| version = "1.17.0" |
There was a problem hiding this comment.
The version update is incomplete. The ui/desktop/package.json file still has version "1.16.0" on line 4 and needs to be updated to "1.17.0" to keep versions consistent across the codebase.
katzdave
approved these changes
Dec 18, 2025
Collaborator
|
So what happened? Did you trigger the release pipeline manually; It usually gets triggered from merging that branch now right? |
alexhancock
force-pushed
the
alexhancock/version-bump-for-1.17
branch
from
4a59751 to
2e6b9ac
Compare
alexhancock
force-pushed
the
alexhancock/version-bump-for-1.17
branch
from
2e6b9ac to
9f167a2
Compare
alexhancock
force-pushed
the
alexhancock/version-bump-for-1.17
branch
from
9f167a2 to
fc51409
Compare
| "name": "Apache-2.0" | ||
| }, | ||
| "version": "1.16.0" | ||
| "version": "1.17.0" |
There was a problem hiding this comment.
The version has been updated in openapi.json, but the corresponding version fields in ui/desktop/package.json (line 4) and ui/desktop/package-lock.json (lines 3 and 9) are still at "1.16.0". These should also be updated to "1.17.0" for consistency.
Suggested change
| "version": "1.17.0" | |
| "version": "1.16.0" |
zanesq
added a commit
that referenced
this pull request
Dec 18, 2025
* 'main' of github.com:block/goose: (28 commits) Clean PR preview sites from gh-pages branch history (#6161) fix: make goose reviewer less sycophantic (#6171) revert /reply to previous behavior (replacing session history) when full conversation provided (#6058) chore: manually update version (#6166) Integrate pricing with canonical model (#6130) Regenerate canonical models when release branch is created. (#6127) fix: use correct parameter name in read_module handler (#6148) docs: blog for code mode MCP (#6126) test: add ACP integration test (#6150) docs: auto download updates (#6163) fix: respect default_enabled value of platform extensions (#6159) docs: skills (#6062) fix: add conditional configuration for GOOSE_BIN_DIR in PATH (#5940) Update dependencies to help in Fedora packaging (#5835) fix: make goose reviewer less bad (#6154) docs: create/edit recipe button (#6145) fix(google): Fix 400 Bad Request error with Gemini 3 thought signatures (#6035) fix: we don't need to warn about tool count when in code mode (#6149) deps: upgrade agent-client-protocol to 0.9.0 (#6109) fix(providers): fix for gemini-cli on windows to work around cmd's multiline prompt limitations #5911 (#5966) ... # Conflicts: # ui/desktop/src/api/sdk.gen.ts # ui/desktop/src/hooks/useAgent.ts
dianed-square
pushed a commit
that referenced
this pull request
Dec 19, 2025
bkvarda
pushed a commit
to bkvarda/goose
that referenced
this pull request
Dec 19, 2025
Signed-off-by: Brandon Kvarda <brandon.kvarda@databricks.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We need to do this this time because the PR for 1.17.0 couldn't merge cleanly
#6131
We can update the release workflow to only actually merge a version bump like this in the future to avoid conflicts, but we should do this manually for this one