Strange. I commented-out your include scripts (because these are required to do a full compile) and the project does not trigger any code-signing in SB 2019 here…
Just for fun, to test it, when you comment out your include scripts - one by another - does this change anything? Perhaps one of the .sbi include scripts cause it, but I have never ever seen this before.
very interesting. Since 2010 (15 years ago ) the SetupBuilder compiler can detect a .sbp project file renamed to a .sbi include script and then stop the compilation process with a fatal error. Your “load files.sbi” include script (created with SetupBuilder 6.9.2454) is such a renamed project file. But SetupBuilder (including the new 2025 BETA) can’t detect this one.
I’ll fix it in SetupBuilder 2025. Thank you for your help and for bringing this to my attention! I removed the “project” file specific properties from your “include” script and sent it via email.
I have received the email and indeed that has fixed my issue.
It would be better I think to offer to change the spb to an sbi, and warn that it’s irreversible. Or have a small utility to do this.