Changelog would probably be nice on the updater too

The Internet Download Manager's updater could be a useful reference. They parse the txt file from server btw.

Could be possible by parsing the HTML content from the Changelog wiki. I found a JS from here, not familiar with C# so dunno how to integrate this.

This would be a nice feature to have, but in the current state it's a bit hard.

We will need:

• An API endpoint to query the changelog (or possibly give the emulator the full changelog and makes it parse it)
• A process to push changelog information with new version (changelog is constructed after a release is made at the moment)

A very good idea.
It would allow you to see in real time the maj that has been done.
It may take some time to set up, but once the routine is done, it will become a habit.

I hope one day the Pr will be reopened to do this

Couldn't the changelog be autoconstructed in the release workflow based on the merged PRs for a given release?
Would ofc require a consistent PR structure that has the needed information.
A cleanup pass could be done manually post release but a preliminary log would fill the gap.

This would be a nice feature to have, but in the current state it's a bit hard.

We will need:

• An API endpoint to query the changelog (or possibly give the emulator the full changelog and makes it parse it)
• A process to push changelog information with new version (changelog is constructed after a release is made at the moment)

Actually you can use Github REST API to query for the latest releases (in your release-channel-master repo), then extract the value from the body key. But to do that, you should write (descriptive) changelogs in that repo like you guys always have done in the wiki (otherwise it will show “For more information about this release…”). If possible I will try some C# code and test before opening PR.

Proof of concept: yell0wsuit#1.

Need the Ryujinx team to update the release description in their release-channel-master repo.

Also need to add a delay about 10-15 min so the team has some time to update the release description, otherwise users will see the very generic description lol.

If we're going to do this, the description should be added on merge, or before. Otherwise I don't think it will work well as someone will inevitably forget to update it. Also there would always be a time gap where there's no description which is also not good.

need to add a delay about 10-15 min so the team has some time to update the release description

To avoid this, I asked for a kind of semi-automated changelog, where we could type the change and description in advance somewhere and a bot would add the date and version and publish it once the changes are pushed, so the in-emulator changelog could grab that, but I don't even know if that's possible or how much work it would be.

Other emulators just grab the commit name and roll with that, which is probably much easier, but most users won't get much of what it means.

The best thing that I can think right now is that a bot looks for the last message from any repo member with some tag followed by a description. The text would then be used for the release description.

I decide to revisit this and I seem to get it working, even though it's in the update window (not in the About window).

The only problem is that the changelog cannot be localized.

I decide to revisit this and I seem to get it working, even though it's in the update window (not in the About window).

The only problem is that the changelog cannot be localized.

The changelogs are not localized so you're fine.

I kinda did it. Will push to Github later.