-
-
Notifications
You must be signed in to change notification settings - Fork 412
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
rye self update
always re-downloading binary, even when up to date.
#1033
Comments
A possible fix for this would be to host the checksum of the latest version (preferrably on GitHub) and then use that to validate if the user's binary is up to date or not |
I guess it would be similar to what
|
Exactly. The ideal case would be something like what uv is doing Looking at the the here for the The functionality that we would want is already built into From the little testing that I did with So we have two options if we want to do this
Note: For rustup, instead checksums they have a toml file that they get the latest stable version from and then they compare it to the current version of that the program is running on. This is much simpler than the checksum. I think the team is probably planning on 2 because they did it for For a hotfix, something like what rustup does would be the likely candidate If there is an interest in adding this feature, I would like be assigned to it. |
There's already a
|
Steps to Reproduce
rye self update
Expected Result
It should check and see that it's the latest version and report "Already up to date."
Actual Result
It re-downloads the binary and makes a new virtualenv.
Version Info
Stacktrace
No response
The text was updated successfully, but these errors were encountered: