[Feature request] append artifact to release.

[gengjiawen]

I really enjoy using release-please (thanks for this project). I introduce to my electron project, which need artifact on release

My previous release like this, include binary for auto-updates.

But with release please, I can only get this (this will also break auto-updater for electron).

It would be much wonderful to use artifacts in this case.

[bcoe]

I really enjoy using release-please (thanks for this project)

Thank you 👏

I introduce to my electron project, which need artifact on release

I was talking to my colleague @JustinBeckwith today, about how he'd like a version of release please that handles advanced workflows (in his case, like publishing to npm).

My thinking, is that it would be good to add guides in docs/ that demonstrate complex workflows:

• docs/npm.md: how you wire up a GitHub action, with release-please, to publish to npm.
• docs/electron.md: how you wire up a GitHub action, with release-please, to publish artifacts to the release.

---

Question: when you're creating an electron application, how are the artifacts created, is it a step that happens, e.g., npm run build?

[JustinBeckwith]

FWIW, this is something semantic-release-github supports. I needed this in linkinator to attach release binaries generated by vercel/pgk as part of the release.

[gengjiawen]

My thinking, is that it would be good to add guides in docs/ that demonstrate complex workflows:

This looks very good to me.

Question: when you're creating an electron application, how are the artifacts created, is it a step that happens, e.g., npm run build?

yarn electron-build

[Oyabi]

Hi, any update or work around on this issue?

[slurdge]

This is also something I need. Right now it breaks my building of artifacts on https://github.com/slurdge/goeland/, even though there is a tag created.