[GH-ISSUE #62] Update to new version #41

Closed
opened 2026-02-28 14:46:33 +03:00 by kerem · 3 comments
Owner

Originally created by @Ciavarella on GitHub (Oct 14, 2019).
Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/62

First of all, i have tried your tui now for a while and i gotta say that i love it! I follow every new feature and i am really happy to see all the progress.

Sorry if this is not the right forum but do you have a command that updates the tui to the latest version? Or should this command check the latest version when it starts?

Example: I have the older version that does not have "next track". Could it be a good thing to implement a check for your latest version so i know that i could update it? I have to check everything manually now.

Solution: Check if the user has the latest version and ask if you want to update. When new update is installed maybe have some text with new implemented features?

Originally created by @Ciavarella on GitHub (Oct 14, 2019). Original GitHub issue: https://github.com/Rigellute/spotify-tui/issues/62 First of all, i have tried your tui now for a while and i gotta say that i love it! I follow every new feature and i am really happy to see all the progress. Sorry if this is not the right forum but do you have a command that updates the tui to the latest version? Or should this command check the latest version when it starts? Example: I have the older version that does not have "next track". Could it be a good thing to implement a check for your latest version so i know that i could update it? I have to check everything manually now. Solution: Check if the user has the latest version and ask if you want to update. When new update is installed maybe have some text with new implemented features?
kerem closed this issue 2026-02-28 14:46:33 +03:00
Author
Owner

@Rigellute commented on GitHub (Oct 14, 2019):

Thank you, I greatly appreciate it.

Regarding updates, my current workflow is to build up some unreleased features and then I manually create a release for both brew and cargo.

You can then update with these commands

macOS

brew upgrade spotify-tui

linux

cargo update spotify-tui

I plan to manage the versions through these package managers, rather than implementing an autoupdating feature.

Perhaps one day we will achieve continous development - on every merge to master a new release is auto created.

I also like your idea of showing the release notes when you start up spt, I will explore that!

<!-- gh-comment-id:541562890 --> @Rigellute commented on GitHub (Oct 14, 2019): Thank you, I greatly appreciate it. Regarding updates, my current workflow is to build up some unreleased features and then I manually create a release for both `brew` and `cargo`. You can then update with these commands #### macOS ```sh brew upgrade spotify-tui ``` #### linux ``` cargo update spotify-tui ``` I plan to manage the versions through these package managers, rather than implementing an autoupdating feature. Perhaps one day we will achieve continous development - on every merge to `master` a new release is auto created. I also like your idea of showing the release notes when you start up `spt`, I will explore that!
Author
Owner

@Rigellute commented on GitHub (Oct 14, 2019):

Also, if you want to stay on the bleeding edge, you can clone this repo and run in development mode.

You can follow these instructions to get setup.

<!-- gh-comment-id:541563473 --> @Rigellute commented on GitHub (Oct 14, 2019): Also, if you want to stay on the bleeding edge, you can clone this repo and run in development mode. You can [follow these instructions](https://github.com/Rigellute/spotify-tui#development) to get setup.
Author
Owner

@Ciavarella commented on GitHub (Oct 14, 2019):

Great! Sorry for being unclear there for a moment, i know how to upgrade but i just thought that it would be nice to have an autoupdating feature but the brew upgrade spotify-tui command works fine to!

Regarding release notes i think that would be awsome!

Again, great work! Very impressive!

<!-- gh-comment-id:541575677 --> @Ciavarella commented on GitHub (Oct 14, 2019): Great! Sorry for being unclear there for a moment, i know how to upgrade but i just thought that it would be nice to have an autoupdating feature but the `brew upgrade spotify-tui` command works fine to! Regarding release notes i think that would be awsome! Again, great work! Very impressive!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/spotify-tui#41
No description provided.