Changelog in Beta Channel about dietpi

[MichaIng]

While I partly agree, it is at least difficult to achieve. This changelog is shown in a pretty trivial way, downloading the text file from here: https://github.com/MichaIng/DietPi/blob/beta/CHANGELOG.txt
And this shows the changelog for each "release" version, no matter whether its released, in beta or dev.

An argument why I would leave it like it is, is that beta testers should test the code used in next release as much as possible. Running things in scripts differently based on beta vs stable DietPi version, would mean that the code used by the stable version is untested.

For the same reason we do no incremental patches between beta versions, but always run the full set of patches from last stable release on. You can even see in the updater output, that it reduces the subversion by 1, hence treats it as if it was one DietPi release earlier. This way we can assure that all patches done on stable versions were well tested. And as a good side effect we can be sure that all patches can be applied multiple times without downsides, i.e. we need to code them like this, so if the updater fails or is terminated for some reason in the middle, there won't be a problem to just re-apply the update with all patches.

Now, the code to see the changelog is probably not a critical one that needs much testing, and we have a benefit from making beta testing a seamless experience. But it would definitely require some good ideas and additional maintenance efforts to maintain dedicated incremental release notes between beta versions, which can be downloaded/parsed easily in shell scripts. We cannot just use the HTML page of the related GitHub pull request, because it is not really parseable, and also I had no idea how the updater should know/find out which PR to look for 🤔.