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

Auto-update or warning that a new version is available #386

Closed
mawoka-myblock opened this issue Apr 29, 2021 · 9 comments
Closed

Auto-update or warning that a new version is available #386

mawoka-myblock opened this issue Apr 29, 2021 · 9 comments

Comments

@mawoka-myblock
Copy link

Is your feature request related to a problem? Please describe.
Nope

Describe the solution you'd like
If I install croc via the install-script it should check before sending/receiving if it is up to date so I don't get any errors because the server was updated

@schollz
Copy link
Owner

schollz commented May 1, 2021

I'd accept a PR for this

@mawoka-myblock
Copy link
Author

Sadly I can't code Go

@tomkukral
Copy link

How should croc discover latest release? From github API? I think it should be optional parameter as doing another call to github API can be considered harmful.

@mawoka-myblock
Copy link
Author

Yea, but I mean, for example, croc receives an update, but the client throws an error because the client and the server are incompatible. I would like to see something like you client isn't up-to date. Please update croc. instead of an error Nobody understands.

@Kodden585
Copy link

How should croc discover latest release? From github API? I think it should be optional parameter as doing another call to github API can be considered harmful.

I think it would be suitable for the relay to notify the user about this.

Copy link

Stale issue message

@mawoka-myblock
Copy link
Author

Still relevant

Copy link

Stale issue message

@mawoka-myblock
Copy link
Author

Still relevant

@schollz schollz closed this as not planned Won't fix, can't repro, duplicate, stale May 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants