You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Doing a debug upload to Modrinth doesn't list the files uploaded unlike its CurseForge counterpart
Output:
Scanning <JARFILE> for presence of fractureiser
Full data to be sent for upload: {
"name": "[1.20.6 NeoForge] v 1.0.0",
"versionNumber": "1.0.0",
"changelog": <STRIPPED>,
"dependencies": [],
"gameVersions": [
"1.20.6"
],
"versionType": "release",
"loaders": [
"neoforge"
],
"featured": false,
"projectId": <STRIPPED>
}
I wasn't sure if this was intentional or not, I was testing the new addAdditionalFiles from #5 (comment) and wanted to test that the additional files are still uploaded to Modrinth as the documentation isn't clear on this (it says it's only supported on CF). I've seen from the code that it is, but wanted to double check.
The text was updated successfully, but these errors were encountered:
I don't even remember adding the additional files to modrinth 😅
I actually saw this as well. What's strange, is we use the same method as Minotaur (modrinths plugin) to print the debug output, so it is very strange that the files are not included.
project.getLogger().lifecycle("Full data to be sent for upload: {}", gson.toJson(builder.build()));
Will have to see if I missed something somewhere.
Side Note: I see my comment on the addAdditionalFiles is misleading. The changelog and display name override is only supported on CurseForge (as far as I know, modrinth doesn't support this).
Doing a debug upload to Modrinth doesn't list the files uploaded unlike its CurseForge counterpart
Output:
I wasn't sure if this was intentional or not, I was testing the new addAdditionalFiles from #5 (comment) and wanted to test that the additional files are still uploaded to Modrinth as the documentation isn't clear on this (it says it's only supported on CF). I've seen from the code that it is, but wanted to double check.
The text was updated successfully, but these errors were encountered: