tracking remix release changes has become hell

[akomm]

I'm currently on 1.3.3 and wanted to check what changed. It was previously already spammed fully with this:

But now instead of (because its monorepo and you up the versions synchronously) writing at least the changes in the release, you also delegate to every single package individually:

I wonder, did I miss something, or is this how its going to be in every release?
I used search on the docs page in hope that there is an overview of some sort, but didn't find any.

Thanks in advance

[akomm]

One thing I'v just noted. I usually switched from releases to tags view, becaue the experimentals also appeared in released. But it appears the release view is now clear of the experimentals. I'm pretty sure it was not before, the reason why I switched to the more compact tags view. Thats good.

[sergiodxa]

I agree, I watch the repo for releases to know when there's a new release and read the change log, so I know what changed before upgrading, now it's really hard and every release creates a lot of notifications.

I wonder if the docs could track the change log in an automated way and show it there maybe, so instead of keeping track of the GitHub release it should be possible to read on the docs the stable ones.

[kiliman]

I understand the desire to automate as much as possible, but I think release notes is something that would benefit from the human touch. I'm sure there are many people that would volunteer to consolidate the CHANGELOGs into a more useful document.

[moishinetzer]

I understand the desire to automate as much as possible, but I think release notes is something that would benefit from the human touch. I'm sure there are many people that would volunteer to consolidate the CHANGELOGs into a more useful document.

👋 if devs see this please reach out to me, i'm more than happy to do this

[sergiodxa]

I understand the desire to automate as much as possible, but I think release notes is something that would benefit from the human touch. I'm sure there are many people that would volunteer to consolidate the CHANGELOGs into a more useful document.

I said to do it in an automated way to don't add more work to the team, and since the release notes are already written in the GitHub release in theory if they filter non stable releases they should be able to get all release notes.

But if it needs to be done by hand and it's not a lot more of work that would work yeah.

[akomm]

Looks like someone has added changes to the release (or at least improved it with link to packages that have changes too). Thanks!

https://github.com/remix-run/remix/releases/tag/remix%401.6.5