Liteloader 1.10.2 targets Mixin v0.6.8 in maven (and thus forgegradle), but the release actually includes 0.5.17
The POM for Liteloader 1.10.2 (link) claims that liteloader targets mixin 0.6.8-SNAPSHOT, and it looks like the code was also changed to use that version. However, the actual release (1.10.2 stable) targets mixin 0.5.17.
This is problematic because I updated all of my mixin minVersion values based off of the version reported in gradle dependencies — but never actually tested outside of my development environment. So the release ended up being nonfunctional for users, even after they update to the latest liteloader release (unless I'm missing a development release I can point them to). This could really be problematic if 0.6.8 generated code that was incompatible with 0.5.17 (which does not seem to be the case, but is the reason I updated minVersion; a different release got updated in a way that made generated code no longer backwards compatible and I hadn't updated minVersion).
Please let me know if there's a release I should be directing users to, or if I should just downgrade the minVersion to 0.5.17 even though I'm internally targeting a newer version.
-
The release on maven should match the release on the website unless something has gone wrong with the upload. SNAPSHOT builds are available via Jenkins (click the "see all snapshots" button the download page) and should always match the current branch head.
I will check the release version in case there was some issue with publishing it, but most of this is set to happen automatically when I build it so some portion of infrastructure has failed if the release doesn't match the maven.
