Publish release without rebuilding

[just-paja]

• [x] I have read the contribution documentation for this project.
• [x] I agree to follow the code of conduct that this project follows, as appropriate.
• [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.

Is it possible to publish artifacts without having to rebuild everything? I'm trying to just take all the artifacts as built on CI and shove them up the Microsoft GitHub release.

Still using version 5

What command line arguments are you passing?

electron-forge publish --auth-token {theToken}

Naturally, when I run the command, it fails on me because it is already running on a different "machine", one that does not have capabilities to build packages.

This is how the build flow looks like:

What does your config.forge data in package.json look like?

"config": {
    "forge": {
      "make_targets": {
        "win32": [
          "squirrel"
        ],
        "darwin": [
          "zip"
        ],
        "linux": [
          "deb",
          "rpm"
        ]
      },
      "electronPackagerConfig": {
        "packageManager": "npm",
        "asar": true
      },
      "electronWinstallerConfig": {
        "name": "radio_drama_soundboard"
      },
      "electronInstallerDebian": {},
      "electronInstallerRedhat": {},
      "github_repository": {
        "owner": "just-paja",
        "name": "radio-drama-soundboard"
      },
      "windowsStoreConfig": {
        "packageName": "",
        "name": "radiodramasoundboard"
      }
    }
  }

[MarshallOfSound]

@just-paja Yes, we have built-in support for this.

# This will make the artifacts and not publish them
electron-forge publish --dry-run

# This will publish the result of the dry run
electron-forge publish --from-dry-run

You need to make sure you persist and restore the built files and the the dry run JSON files

[just-paja]

Thank you, @MarshallOfSound. I will try this and report back.

[just-paja]

Thank you again, @MarshallOfSound. Your suggestion worked. Please consider renaming things. I wouldn't expect a dry run to produce anything.

[RaffaeleSgarro]

If the magic flag still --dry-run/--from-dry-run? It's not documented (beside here) and it's a waste of time when testing deployments.

What is the reason to have one command execute another one?