question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Support publishing to Snapcraft

See original GitHub issue
  • Version: 20.26.0
  • Target: Snap

electron-builder has a snap target, but it seems we still need to manually upload the binary using snapcraft push dist/appname_2.16.0_amd64.snap and then snapcraft release appname 1 stable. Would be nice if electron-builder could handle the publish-step too.

More info: https://docs.snapcraft.io/build-snaps/publish

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Reactions:6
  • Comments:15 (6 by maintainers)

github_iconTop GitHub Comments

4reactions
develarcommented, Jul 10, 2019

Python is not a good language for CLI tools (the same as NodeJS 😉), but at least now snapcraft is available for macOS. I cannot find easily instructions how to install it on Windows without Linux subsystem.

electron-builder 21 forces you to publish to store. A new publish provider snapStore is the default value for snap and your regular publish configuration is ignored unless explicitly specified for snap (under key snap).

electron build service cannot be used to publish snap for poor Windows users, who cannot migrate to a normal OS, because I don’t want to take responsibility for credentials. Maybe later electron-builder will produce a special plugin for snapcraft, so, you will be able to use official build service from Canonical to build and publish your snap. I cannot predict when it will be implemented and will be implemented or not.

I like how snapcrat is developer friendly (shame on you, bloody Apple and not so bloody but still, MS).

snapcrat push produces correct and clear error messages, so, electron-builder is not forced to add another layer of error handling.

It will be released in 2 days.

2reactions
rasgo-cccommented, Oct 15, 2020

Quoting @adam-lynch , on issue #4982, you can disable it by providing a generic provider:

You can also set snap.publish to: { provider: “generic”, url: “https://anydummyurl.com” }

Read more comments on GitHub >

github_iconTop Results From Across the Web

About Publishing - Snapcraft
Snapcraft lets you build with the tools you already use · Publish from your developer workstation · Publish with our Build service ·...
Read more >
Releasing to the Snap Store | Snapcraft documentation
Once you have a snap that works under strict or classic confinement, you're ready to publish the snap in the Snap Store where...
Read more >
Releasing your app | Snapcraft documentation
Publishing process. To get started, first register a name for your snap in the Snap Store. Return to the terminal and the location...
Read more >
Want to publish a snap? Here's a list of dos and don'ts
Creating a snap isn't just a matter of declaring instructions in the snapcraft.yaml file (recipe), which will be used to create the final ......
Read more >
Build and publishing example | Snapcraft documentation
Risk - enables publication of multiple supported releases of the snap under the same snap name. Branch - are optional and hold temporary ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found