Skip to content
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

brew version is outdated #1054

Closed
KorayUlusan opened this issue Sep 14, 2021 · 7 comments
Closed

brew version is outdated #1054

KorayUlusan opened this issue Sep 14, 2021 · 7 comments
Labels
🐛 bug Something isn't working

Comments

@KorayUlusan
Copy link

KorayUlusan commented Sep 14, 2021

Current version is 2.6.2 but when I try to install it with homebrew its 2.5.0

$ brew info khanhas/tap/spicetify-cli
khanhas/tap/spicetify-cli: stable 2.5.0
Command-line tool to customize Spotify client

and also, when is the new release?

@KorayUlusan KorayUlusan added the 🐛 bug Something isn't working label Sep 14, 2021
@afonsojramos
Copy link
Member

Until @khanhas is back we can't update that. Is there no option on brew to install what is currently on master?

@KorayUlusan
Copy link
Author

The thing is it's not from this repo, but from khanhas/homebrew-tap, which hardcoded url "https://github.com/khanhas/spicetify-cli/archive/v2.5.0.tar.gz". So no, cannot install what is currently on master.

I don't know if there is an technical reason behind this decision, but to me it makes more sense to have it in this repo.

@TheGeeKing
Copy link
Contributor

khanhas/homebrew-tap, which hardcoded url "https://github.com/khanhas/spicetify-cli/archive/v2.5.0.tar.gz".

If you check the PR someone changed the code to download the last version.

and also, when is the new release?

No release date for the moment, but you can check the PR or the discord on how to have a prerelease of 2.6.3

@afonsojramos
Copy link
Member

he thing is it's not from this repo, but from khanhas/homebrew-tap

@KorayUlusan Unfortunately, I do not have access to that repo either

@nullmaxwell
Copy link

Opened an issue on that repo and linked it to this one. like @TheGeeKing said, there's an open pull request there that should solve the issue once it's approved.

@TheGeeKing
Copy link
Contributor

Good. @KorayUlusan, you can close this issue now.

@itsmeow
Copy link
Member

itsmeow commented Oct 1, 2021

Updated now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants