We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Tim requested something in the dApp that shows the users they need to update and also allows them to update from within the dApp.
I see these as two features:
Notification - The probably easier thing to implement
In-dApp updating - The definitely harder thing to implement
The text was updated successfully, but these errors were encountered:
@acnebs I vaguely remember that you did work on some notifications of new versions when you were working on auto update? did you?
Sorry, something went wrong.
Yep, I was toying with it, but quickly abandoned it since we had no automated build process and auto-updates weren't going to work anyway.
But now that we have the GH Workflows I'm happy to get at least a notification up and running at the very least. 👍
@acnebs yes that would be great, if people just got notified and got a link to where to get the new update from 🙏🏽 Thank you
Apologies, found this associated issue: #64
Looks like we need signing auth to proceed with in-dapp updates.
Lets close this issue when we have in-dApp notifications and leave Issue 64 open until we get in-dApp updates.
No branches or pull requests
Tim requested something in the dApp that shows the users they need to update and also allows them to update from within the dApp.
I see these as two features:
Notification - The probably easier thing to implement
In-dApp updating - The definitely harder thing to implement
The text was updated successfully, but these errors were encountered: