You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With all of the groundwork taken care of, we can actually create automatic updates. This will involve:
Checking the latest version available from the public repository (https://volta.sh/latest-version) and comparing with the currently running version
If there is a newer version available, downloading and unpacking the binaries into their expected locations
After the new binaries are available, the migration behavior will take care of any necessary changes the next time volta or a shim is executed. There are a couple considerations for the implementation:
It shouldn't have a significant effect on the hot path of running a shim, we don't want users to be waiting for an update when all they did was run ember --version.
We shouldn't be propagating any errors to the user's terminal, since they shouldn't have to think about the fact that the update is running.
We don't want to check every time the user runs a tool, we should limit it to ~once per day, at most.
We need a way of detecting managed environments, so that we can skip checking for updates when the version is being handled by an internal IT team.
The text was updated successfully, but these errors were encountered:
With all of the groundwork taken care of, we can actually create automatic updates. This will involve:
After the new binaries are available, the migration behavior will take care of any necessary changes the next time
volta
or a shim is executed. There are a couple considerations for the implementation:ember --version
.The text was updated successfully, but these errors were encountered: