Adds a renaming script to rename the binaries with our
Regular release naming scheme, and updates the Cirrus config
to run said renaming script.
De-facto codifies our existing, officially unofficial naming scheme
with a bit of automation.
We can always revise this down the line
if consensus changes for how to name these files.
Just a little institutional knowledge to unburden team members with,
via the (sometimes double-edged sword...) of automation.
Effectively: install ppm's dependencies (and run its postinstall
scripts) with Yarn, not npm, on Windows.
This makes the installation of ppm's dependencies consistently use
Yarn, not npm, in Cirrus CI. Consistent for all OSes/arches we build
for in Cirrus.
(* Although, at some level the postinstall scripts are run via npm as
a subprocess of node as a subprocess of Yarn in a shell/console
sub-process... Yes, in my opinion, ppm's postinstall scripts are way
too complicated...)
ALSO: This fixes an oversight in PR 239 where the build script of the
wrong project (ppm instead of core) was being run at one point, again
on Windows.
So, this should make it so Pulsar's core dependencies are built for
the correct Electron version instead of built for Node... Oops!
Should fix an obscure issue where ppm's postinstall script exits out
half-way through without resuming under Yarn, but completes fully
under NPM.
Probably has something to do with Yarn handling process.exit()
differently than NPM does, in the postinstall script/its sub-scripts.
(Perhaps Yarn avoids running sub-processes of Node nested as deeply
as NPM does? Thus process.exit() exiting a higher Node process that we
expect to still have work to do later in the main postinstall script?
Not totally sure. This is just a guess.)