We now have new a brand CI/CD pipeline responsible for building IPFS Desktop (#1657, #1659).
Before we ship v0.13, let's have more eyes on platform-specific packages.
If you have spare time between now and Monday (~5min):
https://bafybeiamxdw3qlecv2mryeojfn46kv32t3nt2a6zajm6wotjadznrtvutm.ipfs.dweb.link/ipfs-desktop-0.13.0-rc2
Click to expand
If you happen to run Linux, make sure to include the name of distro and Desktop Environment you are running.

_Our team will be back on Monday,
ready to squash any bugs blocking the release_
closes #1153
Mac here. All worked as expected for importing both via Import > Folder and just drag/drop, except the drawer gave me an "NaN" while uploading:

Tested .deb on Ubuntu 20.04 stock version.
Import button and dragging on Files screen both work as expected, except I got cheese NaNed like @jessicaschilling .

(Fur your infurmation, it wasn't a cat picture pur say, so your mileage meow vary.)
Snap: same story

Worth noting: My previously addded files and folders are not available.
I think it's because snap sets up its own repository, isolated from other apps...
Also, when dragging, It wrote that I imported 0 items:

EDIT: @lidel
I had to install it with snap install --dangerous otherwise I get:
> snap install Downloads/ipfs-desktop-0.13.0-linux-amd64.snap
error: cannot find signatures with metadata for snap
"Downloads/ipfs-desktop-0.13.0-linux-amd64.snap"
IPFS-Desktop-0.13.0.dmg - it went smoothly.
Imported NaN Items as mentioned above, for both import via menu option and import via file drop.
I managed to get hold on Windows 10 laptop and both installing for single user and globally on the OS seems to work as expected. Binary is signed.
Worked fine on Windows 10 (1809). Got a message saying Imported NaN items after adding a file, but apart from that everything was fine.
Thank you all! :pray:
I've filled https://github.com/ipfs-shipyard/ipfs-webui/issues/1659 for the NaN thing. It is not related to Electron, but a ux bug in webui (confirmed it in Firefox).
While NaN looks bit awkward, it is shown only when more than one file was imported.
I don't think this small UX nit should block the release that ships go-ipfs 0.7.0 with Ed25519 keys and DHT improvements.
@jessicaschilling Let's discuss this later today during triage
Just tested .AppImage on Ubuntu 20.04
It worked once perfectly with import. Even without the NaN problem:

But most of the time there is the NaN/ 0/ 1 problem:
One dragged file:

Sometime it displays this :

... then this after a few seconds :

Other than that it works.
Update: @Gozala is troubleshooting - ideally we'd patch this before releasing a new Desktop, as it's a highly visible UX flaw even if it's not breaking functionality.
@Gozala fixed theNaN bug (https://github.com/ipfs-shipyard/ipfs-webui/pull/1660), and we switched to webui v2.11.3 (https://github.com/ipfs-shipyard/ipfs-desktop/pull/1666).
@jessicaschilling @johnnymatthews @bertrandfalguiere @olizilla
please repeat the test using RC2 version :pray:
IPFS Desktop-0.13.0.dmg: NaN issue is gone.
Note that I've filed https://github.com/ipfs-shipyard/ipfs-desktop/issues/1668 for less-than-ideal placement of Mac window controls vis-a-vis IPFS cube in the left nav.
AppImage: OK
.deb: OK
.snap: must be installed with the --dangerous flag (I guess it won't be needed once on the snapstore?). Files are in a different place than with other installs, and the peer ID is different. Otherwise, OK
@bertrandfalguiere thank you! Yes, --dangerous won't be needed when it lands on snapstore. Snap has its own philosophy regarding paths, so those discrepancies are expected.
@jessicaschilling Electron had a bunch of security fixes recently (v9.3.1, v9.3.2), so I've updated us to 9.3.2 and created RC3. I've also switched to webui v2.11.4 so https://github.com/ipfs-shipyard/ipfs-desktop/issues/1668 should be fixed on macOS.
ipfs-desktop-0.13.0-rc3/.tar.xz)@lidel tested on MacOS and looks good 馃憤
@lidel @rafaelramalho19 Confirmed OK on MacOS here as well.
Thank you all for help! Shipping it to autoupdate channel.
v0.13.0 :ship: :dash:
Most helpful comment
Update: @Gozala is troubleshooting - ideally we'd patch this before releasing a new Desktop, as it's a highly visible UX flaw even if it's not breaking functionality.