confused_techie

I do want to add, just to make it clear. We have been signing our binaries with no issue for several months, and within the last month, with zero changes...

> I think Apple changed something. It's happened before to me. Interesting, sounds like we have to explore that possibility. Ideally it's something that can be changed on our end....

@mmaietta I really do appreciate your support here, even if not your primary area of focus. I'll go ahead and give a try to what you've suggested, but I really...

@davidmurdoch I want to let you know, we just had a successful build on GitHub Actions with `electron-builder` on macOS, by one weird thing. We skipped the `setup-node` action and...

@davidmurdoch Alright, I take this back slightly. One of our awesome developers was able to find the exact cause, and fix our issues with a single commit diff. Turns out...

@DeeDeeG You make some good points about issues with adding Pulsar to the path via a machine install, but at the very least I would expect some sort of error...

Thanks a ton for reporting this! But, and someone feel free to correct me if I'm wrong, pretty sure this is expected behavior. When launching Pulsar from the command line...

So just checking this isn't the behavior on Atom's last released versions. Although, launching Atom via the CLI also doesn't provide any output to the console of what's going on,...

@DeeDeeG Looking into the `.bat` is a great idea, although I'll say it's probably not the fault of `electron-builder` as the output looks and behaves identical when running Pulsar for...

Yeah seems that has happened. Effort to bundle core packages has been shared recently, and I was not aware any were missing. More than happy to ensure everything is getting...