[Feature Request]: Log update history for easier regression identification #12273
Labels
Enhancement / Feature Request
FR: Medium Complexity
Requires some codebase knowledge. A proficient developer should be able to manage.
FR: Medium Priority
The request can bring some quality of life to the average emulator user.
Description
Keep track of a log of the user's update history in a local file.
Reason
If a typical user comes to us about a regression after an update, they almost certainly don't remember what version they were on before the regression, and there's seemingly no way to retrieve that information. This would make it vastly easier for both the user and for the contributors, because right now, we can make no assumptions about what version a user updated from and simply have to bisect it. This is especially true if the issue is qualitative (e.g. "it's a lot slower") or not easily reproducible.
Examples
For example, if I first start out on v2.1.50, then I update to v2.3.4, then I update to v2.3.140, the file might look something like:
The text was updated successfully, but these errors were encountered: