Sudara

Finally coming up on personally needing this. Since we have all important env variables already exported from cmake, I'm considering having the xml be explicit in the repo and using...

@zsliu98 Thanks for sharing! > if we want different targets, we may have to edit the XML file each time. Yeah, that's definitely the trade-off...I think if all variables are...

I think you are saying that "most of the time I push to CI, I don't need a code signed, packaged release with all formats" and proposing that we push...

Yes, that probably be documented or even just commented out of the xml. I think those are better options than providing a background image that people would then have to...

> sometimes you run into crashes that are extremely hard to reproduce (even with the same random seed) or only occur in release builds. In these scenarios being able to...

NIce! RIP `kill9WithSomeMercy`

Definitely worth exploring. I've never personally looked into it, but I've always assumed as a dll inside a host, the options are limited: https://forum.juce.com/t/crash-reporting-from-within-a-dll-audio-plugin/15485/19?u=sudara On macOS, I've heard of people...

For pamplejuce, sounds like we should put a timeout on the codesign step (see the pkgbuild step). For the keychain action, are you using your main macos user or a...

Ah yeah, on my own projects I also have my keychain unlocking right before signing. Maybe that's another change worth making to pamplejuce.

These changes were made. Import comes right before codesign and the keychain is now explicitly specified https://github.com/sudara/pamplejuce/pull/176