[BUG] When updating mods to a new MC Version mods wont automatically update

[SirOMGitsYOU]

Describe the bug When changing a Minecraft version (in my example I am upgrading my modpack from 1.18.2 to 1.19) - The mods that were previously found and working for 1.18 get this message, This prevents the "Update all mods" function from working as it just 404's As presumably, it can't figure out what the mod ID is supposed to be.

To Reproduce Steps to reproduce the behavior: (Can use any modpack or even a brand new profile just follow on from step 2 after installing a bunch of mods)

1. Download Stargaze
2. Change the Minecraft version to 1.19
3. Attempt to update all mods using the update all button.
4. no dice.

Expected behaviour Update the mods to the latest (preference respected) version in 1.19

Possible solutions Some ideas of how you would solve this issue, if possible

Screenshots

Operating System:

• OS: Windows
• Version: 11
• Java Version: Java 11
• Minecraft Version: 1.19
• Mod Loader: Forge

Additional Comments This works (for some mods) if you click the manual download button next to the mod disable button, however it is more tedious process to do it one-by-one

[Brittank88]

I mean, the update all mods functionality should at least be fail-soft and update what it can, and then warn about the remaining.

[trevorjd]

FWIW, it might not only be with new MC versions. I upgraded my FTB Unstable 1.20 from v1.3.0 to 1.4.0 which was MC 1.20.1 before and after, and GDL failed to download new mod versions.