-
-
Notifications
You must be signed in to change notification settings - Fork 677
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
Show a breaking changes prompt or notification upon updating, if needed #1162
Comments
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
This looks like it might be a viable library to use: https://github.com/AppDevNext/ChangeLog might be able to use a github action to pull in the changelog on each commit :) |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
Still an issue. |
Is your feature request related to a problem? Please describe.
We should try to better inform users about breaking changes so they know what is expected of them. If possible, show the whole change log for the current version but breaking changes should be highlighted at the top. Although we have a blog post detailing this, not all users see it so its a better experience to inform them some how. We can even consider a notification as not all users will open the app after updating.
Describe the solution you'd like
As PR's come in we should mark them as a breaking change (if required) so we can identify them easily. We should find a good way to prompt users about this. I think a notification might make the most sense, but an in app prompt can also work to ensure they have seen it. We should also include the blog post link in the play store release notes.
Describe alternatives you've considered, if any
The alternative is to expect all users will read either github change log or the blog post.
Additional context
I see users having issues in the forums, reddit and probably eventually on discord. The better we can handle the situation the less upset people can be.
The text was updated successfully, but these errors were encountered: