The first question you need to answer is if your users care. There's no need to implement any functionality or user interface components in order to add something that users don't want or need. That's just more code that needs to be tested and validated. If there's no requirement for this information to be displayed in the application, you're just gold plating the requirements - a known antipattern.
If your users do want this information, you need to determine how to make it available. That should be driven by the users, through requirements that they provide. You seem to want to present it as a tool accessible through the user interface. However, there are many other options that should be considered, and discussed with your users (or the subset of users who might want this information). Possible options include a "changes since last release" in the README or user's manual, a changelog file alongside the README or user's manual, or a web page on the product's website that describes the changes in the latest version with the ability to view changes between latest versions. Depending on the file format that you use for the changes, you could either open that file using the OS-specified application or parse the file and display it in a user interface as well.
Regardless of how you deliver it, don't do it because you want to, but because your users want it. Otherwise, you're just creating work for youself that adds no value to your product.