Some mods format their versions non-semanticly (like 1.2.3-build1).
Instead you sometimes see a part of a string being prefixed to the number.
When running the outdated command, these mods show up as being outdated but the latest version is exactly the same as the one installed.
The issue lies in the prefix. When I need to resolve a version, I first strip all characters before the first digit.
Apparently, I forgot to do this in the outdated command.
Example output:
mcpm outdated
[INFO] Found 6 outdated mod(s):
| Mod | Current | Wanted | Latest |
-------------------------------------------------------------------------------------------------------
| modrinth:audioplayer | 1.21.5-1.13.2 | 1.21.5-1.13.2 | fabric-1.21.5-1.13.2 |
| modrinth:enhanced-groups | 1.21.5-1.7.0 | 1.21.5-1.7.0 | fabric-1.21.5-1.7.0 |
| modrinth:forge-config-api-port | 21.5.1-1.21.5-Fabric | 21.5.1-1.21.5-Fabric | v21.5.1-1.21.5-Fabric |
| modrinth:lithium | 1.21.5-0.16.3-fabric | 1.21.5-0.16.3-fabric | mc1.21.5-0.16.3-fabric |
| modrinth:luckperms | 5.5.4-fabric | 5.5.4-fabric | v5.5.4-fabric |
| modrinth:simple-voice-chat | 1.21.5-2.6.6 | 1.21.5-2.6.6 | fabric-1.21.5-2.6.6 |
Checked 24 mods total
Some mods format their versions non-semanticly (like
1.2.3-build1).Instead you sometimes see a part of a string being prefixed to the number.
When running the outdated command, these mods show up as being outdated but the latest version is exactly the same as the one installed.
The issue lies in the prefix. When I need to resolve a version, I first strip all characters before the first digit.
Apparently, I forgot to do this in the outdated command.
Example output: