-
Notifications
You must be signed in to change notification settings - Fork 2.6k
feat(goose-cli): add feature to disable update #5886
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
@michaelneale Sorry, I messed up the merging stuff in previous PR #5846 This is a fresh attempt :) |
Signed-off-by: Sai Karthik <kskarthik@disroot.org>
Signed-off-by: Sai Karthik <kskarthik@disroot.org>
f8b8176 to
59e840e
Compare
|
Hi, Just a reminder please review this PR :) |
|
Hy! @alexhancock || @michaelneale please review this tiny patch 😅 |
|
looks good - just wanted to know it leaves it as auto update by default? then lets get it in |
|
Hi. Can you explain more about the reason for wanting this? As an implementation it looks OK to me but I am more curious about the motivation in general |
|
@alexhancock As i explained in the summary, It makes it easy to disable the CLI |
|
I saw that, but I was wondering why it's helpful to have a feature that disables this manner of updating goose. Could we make it so if goose is installed from a package repo, users could still update the |
|
@alexhancock it is very common in distributions of linux or other tightly packaged things to only have one wya to upgrade vs each tool doing their own, so I think this is a valid thing as it allows the goose binaries (which are nicely monolithic) to be packaged neatly in distros and not break signatures/security stance etc. If someone installs it via a packaged way, it is fine to expect that to upgrade (you often get that with language runtimes) and user is always free to have their ownb user-land type version of it if they want (node/python have layers of things like that) so no surprise there. |
michaelneale
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think worth it to be distro packaging friendly.
|
@alexhancock eg: |
|
@michaelneale @alexhancock Hope i have resolved all your queries. Good to merge !? 😃 |
Signed-off-by: Sai Karthik <kskarthik@disroot.org>
…erer * origin/main: (26 commits) Don't persist ephemeral extensions when resuming sessions (#5974) chore(deps): bump mdast-util-to-hast from 13.2.0 to 13.2.1 in /ui/desktop (#5939) chore(deps): bump node-forge from 1.3.1 to 1.3.2 in /documentation (#5898) Add Scorecard supply-chain security workflow (#5810) Don't show subagent tool when we're a subagent (#6125) Fix keyboard shortcut conflict for Focus Goose Window (#5809) feat(goose-cli): add feature to disable update (#5886) workflow: enable docs-update-recipe-ref (#6132) fix: filter tools in Ollama streaming when chat mode is enabled (#6118) feat(mcp): platform extension for "code mode" MCP tool calling (#6030) workflow: auto-update recipe-reference on release (#5988) Document recipe slash commands feature (#6075) docs: add GitHub Copilot device flow authentication details (#6123) Disallow subagents with no extensions (#5825) chore(deps): bump js-yaml in /documentation (#6093) feat: external goosed server (#5978) fix: Make datetime info message more explicit to prevent LLM confusion about current year (#6101) refactor: unify subagent and subrecipe tools into single tool (#5893) goose repo is too big for the issue solver workflow worker (#6099) fix: use system not developer role in db (#6098) ...
* 'main' of github.com:block/goose: (22 commits) OpenRouter & Xai streaming (#5873) fix: resolve mcp-hermit cleanup path expansion issue (#5953) feat: add goose PR reviewer workflow (#6124) perf: Avoid repeated MCP queries during streaming responses (#6138) Fix YAML serialization for recipes with special characters (#5796) Add more posthog analytics (privacy aware) (#6122) docs: add Sugar MCP server to extensions registry (#6077) Fix tokenState loading on new sessions (#6129) bump bedrock dep versions (#6090) Don't persist ephemeral extensions when resuming sessions (#5974) chore(deps): bump mdast-util-to-hast from 13.2.0 to 13.2.1 in /ui/desktop (#5939) chore(deps): bump node-forge from 1.3.1 to 1.3.2 in /documentation (#5898) Add Scorecard supply-chain security workflow (#5810) Don't show subagent tool when we're a subagent (#6125) Fix keyboard shortcut conflict for Focus Goose Window (#5809) feat(goose-cli): add feature to disable update (#5886) workflow: enable docs-update-recipe-ref (#6132) fix: filter tools in Ollama streaming when chat mode is enabled (#6118) feat(mcp): platform extension for "code mode" MCP tool calling (#6030) workflow: auto-update recipe-reference on release (#5988) ... # Conflicts: # ui/desktop/src/App.tsx # ui/desktop/src/api/sdk.gen.ts # ui/desktop/src/components/ChatInput.tsx # ui/desktop/src/components/recipes/RecipesView.tsx
Summary
Added a feature to the
goose-clicrate to disable theupdatecommand.Usecase: I have packaged goose for openSUSE Tumbleweed & i had to patch the build to disable update.
This feature comes handy instead of patching the code & quiet helpful for other distro package maintainers as well 🙂
Type of Change
AI Assistance
Testing
Tested manually
Screenshots/Demos (for UX changes)
Before:
After: