[GH-ISSUE #5099] Add upgrade command to upgrade the version #65254

Closed
opened 2026-05-03 20:13:31 -05:00 by GiteaMirror · 2 comments
Owner

Originally created by @chyok on GitHub (Jun 17, 2024).
Original GitHub issue: https://github.com/ollama/ollama/issues/5099

Hi,
This is an excellent project!
Is there any plan to add an upgrade command-line feature?
So that we can use ollama --upgrade or something else to update the version instead of manual download & install it again.
Thanks!

Originally created by @chyok on GitHub (Jun 17, 2024). Original GitHub issue: https://github.com/ollama/ollama/issues/5099 Hi, This is an excellent project! Is there any plan to add an upgrade command-line feature? So that we can use `ollama --upgrade` or something else to update the version instead of manual download & install it again. Thanks!
GiteaMirror added the feature request label 2026-05-03 20:13:32 -05:00
Author
Owner

@igorschlum commented on GitHub (Jun 17, 2024):

It is common for CLI (Command Line Interface) applications to have an --upgrade command or similar functionality to facilitate updating or upgrading the application itself or its components. This feature allows users to easily apply updates or newer versions of the software through the terminal, streamlining the upgrade process.

For instance, in the context of web development frameworks like Angular, the Angular CLI provides an ng update command specifically designed to help keep projects up to date with the latest versions of Angular and its packages. This command simplifies the upgrade process by applying logic defined by packages to ensure the usage of the latest features and to minimize the impact of breaking changes 4.

Similarly, in the context of e-commerce platforms like CS-Cart, the platform offers a command-line interface for upgrading the software. This includes various options such as skipping backups, ignoring certain validators, and disabling interactive modes, providing flexibility and control over the upgrade process. These options are particularly aimed at developers and experienced server administrators who might need to perform upgrades in automated environments or under specific conditions 3.

In summary, having an --upgrade command or equivalent functionality in CLI applications is a common practice, especially in development tools and platforms where frequent updates and version management are crucial.

https://www.phind.com/search?cache=mvsrvz3nahpewt92kjhtn0ft

<!-- gh-comment-id:2174489816 --> @igorschlum commented on GitHub (Jun 17, 2024): It is common for CLI (Command Line Interface) applications to have an --upgrade command or similar functionality to facilitate updating or upgrading the application itself or its components. This feature allows users to easily apply updates or newer versions of the software through the terminal, streamlining the upgrade process. For instance, in the context of web development frameworks like Angular, the Angular CLI provides an ng update command specifically designed to help keep projects up to date with the latest versions of Angular and its packages. This command simplifies the upgrade process by applying logic defined by packages to ensure the usage of the latest features and to minimize the impact of breaking changes [4](https://stackoverflow.com/questions/41403810/how-can-i-upgrade-an-angular-cli-project). Similarly, in the context of e-commerce platforms like CS-Cart, the platform offers a command-line interface for upgrading the software. This includes various options such as skipping backups, ignoring certain validators, and disabling interactive modes, providing flexibility and control over the upgrade process. These options are particularly aimed at developers and experienced server administrators who might need to perform upgrades in automated environments or under specific conditions [3](https://docs.cs-cart.com/latest/upgrade/upgrade_via_console.html). In summary, having an --upgrade command or equivalent functionality in CLI applications is a common practice, especially in development tools and platforms where frequent updates and version management are crucial. https://www.phind.com/search?cache=mvsrvz3nahpewt92kjhtn0ft
Author
Owner

@jmorganca commented on GitHub (Jun 18, 2024):

Hi @chyok thanks for the issue! On macOS and Windows Ollama has auto update. For Linux, re-running the install script will work – there's no built in updater on Linux because quite a few folks would prefer to rely on package manager systems for this, and it wouldn't make much sense to bake that into the ollama CLI directly. Hope this helps!

<!-- gh-comment-id:2175874059 --> @jmorganca commented on GitHub (Jun 18, 2024): Hi @chyok thanks for the issue! On macOS and Windows Ollama has auto update. For Linux, re-running the install script will work – there's no built in updater on Linux because quite a few folks would prefer to rely on package manager systems for this, and it wouldn't make much sense to bake that into the `ollama` CLI directly. Hope this helps!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#65254