pw release - failed to build release files

[idiot-shinuki]

Just now discovered the pw release command, and while it has no problem creating a changelog, it doesn't actually build the modpack.

❯ pw release files
Generating release files...
Error: failed to build release files: unknown format: all

Somehow, the format "all" is unrecognized. I don't know go syntax, but it can probably be fixed with a for loop that loops through Modrinth and Curseforge. another neat feature would be to have the option to only build for one format. I personally use Modrinth and the mods I find there, and I can't always find those mods on Curseforge. those mods also don't always have a license that permits redistribution of binaries if I were to include the jar file in the Curseforge pack.

Not a big deal to me at the moment though, I use makefile to manage pw commands and I can just add pw release changelog alongside pw batch mr export in the makefile.

[Merith-TK]

Oh, huh, will take a look. Sent from [Proton Mail](https://proton.me/mail/home) for Android.

…

-------- Original Message --------

On Wednesday, 12/17/25 at 17:43 idiot-shinuki ***@***.***> wrote: idiot-shinuki created an issue [(Merith-TK/packwiz-wrapper#7)](#7) Just now discovered the pw release command, and while it has no problem creating a changelog, it doesn't actually build the modpack. ❯ pw release files Generating release files... Error: failed to build release files: unknown format: all Somehow, the format "all" is unrecognized. I don't know go syntax, but it can probably be fixed with a for loop that loops through Modrinth and Curseforge. another neat feature would be to have the option to only build for one format. I personally use Modrinth and the mods I find there, and I can't always find those mods on Curseforge. those mods also don't always have a license that permits redistribution of binaries if I were to include the jar file in the Curseforge pack. Not a big deal to me at the moment though, I use makefile to manage pw commands and I can just add pw release changelog alongside pw batch mr export in the makefile. — Reply to this email directly, [view it on GitHub](#7), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ACPQOXUO2ZKHFSN2HKMJP7D4CIBEXAVCNFSM6AAAAACPMBRBL6VHI2DSMVQWIX3LMV43ASLTON2WKOZTG42DCMBXGQZTOMA). You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[idiot-shinuki]

I've also noticed "Generating mod list for changelog..." in the output of pw release changelog but I don't see any mod list in the CHANGELOG.md file it creates.
I'm using Ultramarine Linux 43 if that helps narrow down any issues, and I used go install to install both packwiz and packwiz-wrapper.

[Merith-TK]

Okay can you try again for your use case? set $GOPROXY=direct when updating your install due to golang proxy issues,.

[idiot-shinuki]

I tried pw release mr and it does its job, but I'm still seeing some weirdness. Instead of the regular naming scheme of modpack-version.mrpack, i'm getting mcversion-modrinth_month-date-HH-MM-SS.mrpack.

Another thing worth noting, pw release changelog seems to generate a mod list in the console output like before, but this time it expects a modlist.md file to include in the changelog. The file isn't there, so I guess it's just not writing the generated data to a file.

Lastly, when I attempt to build a server using the release command, I get a string of errors caused by it not being able to read a resource pack:

Failed to download modpack, the following errors were encountered:
chat-reporting-helper.pw.toml: link.infra.packwiz.installer.request.RequestException$Response$File$FileNotFound: File path not found: resourcepacks/chat-reporting-helper.pw.toml
        at link.infra.packwiz.installer.target.path.PackwizFilePath.source(SourceFile:14)
        at link.infra.packwiz.installer.metadata.IndexFile$File.downloadMeta(SourceFile:40)
        at link.infra.packwiz.installer.DownloadTask.downloadMetadata(SourceFile:110)
        at link.infra.packwiz.installer.UpdateManager.processIndex$lambda-9(SourceFile:300)
        at java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:186)
        at java.base/java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1716)
        at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:570)
        at java.base/java.util.stream.ForEachOps$ForEachTask.compute(ForEachOps.java:293)
        at java.base/java.util.concurrent.CountedCompleter.exec(CountedCompleter.java:759)
        at java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:511)
        at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1450)
        at java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:2019)
        at java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:187)
Update cancelled by user!
Error: failed to build server: failed to build server: failed to install server mods: packwiz installer failed: exit status 1

The file it can't find does indeed exist, and building for Modrinth does work. I'm limited on time, I have work soon and I'll get home at maybe 3 PM EST if I'm lucky. But if you need me to test any other functions of the pw release command, let me know and if my modpack doesn't support that function I'll see if there's a packwiz modpack out there that I can clone.

[Merith-TK]

Ah, so release command is meant for building "releases", like what you would expect in github actions and the like, ifyou just want to build the pack, use build, (pw release changelog is still the one for the changelog)

The changelog part I uh... yeah thats a my bad, working on that.

Also that error is a packwiz-bootstrap jar error, that one I think you should passalong upstream since all the usage of that jar is for with packwrap is to build technic (client) and server zips with all the mod files

[idiot-shinuki]

Also that error is a packwiz-bootstrap jar error, that one I think you should passalong upstream since all the usage of that jar is for with packwrap is to build technic (client) and server zips with all the mod files

I just used the downloaded packwiz-installer-bootstrap jar to run java -jar packwiz-installer-bootstrap.jar pack.toml -s server -g and it builds fine. But I noticed a section in internal/build/server.go that removes client-side folders, including resourcepacks. I think that since resourcepack.pw.toml still exists in the index, packwiz-installer looks for that metafile to read to check whether it's client or server side (since that data is stored in the metafile itself). Since it doesn't exist, the build fails because the index shows files that don't actually exist, making it invalid. Maybe a better way to exclude these files would be to delete the client-side files after it's created in the build directory by packwiz-installer, or to run refresh in the temporary server directory with the client-side metafile directories removed before running packwiz-installer.

[Merith-TK]

Hmm, good catch will take a look at that and see if that is actually the case! Sent from [Proton Mail](https://proton.me/mail/home) for Android.

…

-------- Original Message --------

On Thursday, 12/18/25 at 21:13 idiot-shinuki ***@***.***> wrote: idiot-shinuki left a comment [(Merith-TK/packwiz-wrapper#7)](#7 (comment)) > Also that error is a packwiz-bootstrap jar error, that one I think you should passalong upstream since all the usage of that jar is for with packwrap is to build technic (client) and server zips with all the mod files I just used the downloaded packwiz-installer-bootstrap jar to run java -jar packwiz-installer-bootstrap.jar pack.toml -s server -g and it builds fine. But I noticed a section in [internal/build/server.go](https://github.com/Merith-TK/packwiz-wrapper/blob/bebc39a6416ac9a79538ab4587c6b5276911ebef/internal/build/server.go#L104) that removes client-side folders, including resourcepacks. I think that since resourcepack.pw.toml still exists in the index, packwiz-installer looks for that metafile to read to check whether it's client or server side (since that data is stored in the metafile itself). Since it doesn't exist, the build fails because the index shows files that don't actually exist, making it invalid. Maybe a better way to exclude these files would be to delete the client-side files after it's created in the build directory by packwiz-installer, or to run refresh in the temporary server directory with the client-side metafile directories removed before running packwiz-installer. — Reply to this email directly, [view it on GitHub](#7 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ACPQOXV7L34JYA75WUEB7334COCPXAVCNFSM6AAAAACPMBRBL6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMNZTGU2TMMRRGU). You are receiving this because you commented.Message ID: ***@***.***>

[idiot-shinuki]

I could also just be reading the code wrong, but there's still something weird going on for me to be able to use the jar file directly and have a successful build (which also cluttered my packwiz folder lol), and then have a failed build when using the pw build server command. It could even be something unrelated to excludes, like the way files are moved around leading up to running the jar file.

[Merith-TK]

Does `pw build technic` not have any issues? Sent from [Proton Mail](https://proton.me/mail/home) for Android.

…

-------- Original Message --------

On Thursday, 12/18/25 at 21:30 idiot-shinuki ***@***.***> wrote: idiot-shinuki left a comment [(Merith-TK/packwiz-wrapper#7)](#7 (comment)) I could also just be reading the code wrong, but there's still something weird going on for me to be able to use the jar file directly and have a successful build (which also cluttered my packwiz folder lol), and then have a failed build when using the pw build server command. It could even be something unrelated to excludes, like the way files are moved around leading up to running the jar file. — Reply to this email directly, [view it on GitHub](#7 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ACPQOXSJKRISNJDD24XVGLL4COEOPAVCNFSM6AAAAACPMBRBL6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMNZTGYYDMNBXG4). You are receiving this because you commented.Message ID: ***@***.***>

[idiot-shinuki]

pw build technic does work without any issues.