Skip to content
This repository has been archived by the owner on Jun 14, 2023. It is now read-only.

Wapm update notification doesn't invalidate cache #202

Open
MarkMcCaskey opened this issue Dec 14, 2020 · 0 comments
Open

Wapm update notification doesn't invalidate cache #202

MarkMcCaskey opened this issue Dec 14, 2020 · 0 comments

Comments

@MarkMcCaskey
Copy link
Contributor

The Wapm update notification will display the wrong thing if the value stored there is out of date.

For example if the value in the $WASMER_DIR/.wapm_update.json is 1.0.0-alpha3 and we're on 1.0.0-beta1, it will say to update to an older version because it's different and we don't invalidate the old value stored there.

We should put a relatively short lifetime on the value stored there to prevent this from happening.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant