Add automated checks for newer Grist versions #1508
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We'll need this in its own place so we can call it without going through the install API.
This will be an admin-only config setting, which is fine, as only admins should be informed if there is a newer Grist version available.
Simple function to hit the remote endpoint and save the result to the home db, so it's available to the config.
We keep track of checking task so that we can disable it later when we have a user interface to enable or disable automated version checks.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
We would like to make our self-hosted admins better aware that a newer version of Grist might be available. We'll then display a dismissable banner that informs them in case the version they are running is out of date.
Proposed solution
By default, we'll enable version checking for newer versions, save the results to the config database, and if the version checked is newer, we'll display it in the UI.
Has this been tested?
Screenshots / Screencasts
Coming soon...