Ability to replace the repository from package.json to allow github publishing #529

New Issue

claunia · 2026-01-29T16:42:10Z

claunia commented

2026-01-29 16:42:10 +00:00

Originally created by @stonkie on GitHub (Jul 13, 2020).

I used electron.net to build a Blazor sample that runs on a Raspberry Pi. I automated the CI/CD pipeline using AWS CodeBuild.

Everything works fine and my artifacts are correctly available through S3, but I cannot get electron-builder to publish to github.

It keeps trying to publish to Electron.Net's github repository which is configured in the package.json file although I configured the correct repository in electron.manifest.json .

I believe the electron-builder's documentation is clear that it will always do this (so the repo field is not changeable from electron.manifest.json, but that leaves no way to use github publishing with electron.net .

Would it make sense for electron.net to support some way of configuring the package.json or is this more of an electron-builder issue?

electron.manifest.json

{
  "executable": "RaspberrySour",
  "splashscreen": {
    "imageFile": ""
  },
  "name": "RaspberrySour",
  "author": "Kevin Coulombe",
  "singleInstance": true,
  "environment": "Production",
  "build": {
    "appId": "com.stonkie.RaspberrySour",
    "productName": "RaspberrySour",
    "copyright": "Copyright © 2020 ${author}",
    "buildVersion": "0.0.5-dev",
    "compression": "maximum",
    "directories": {
      "output": "../../../bin/package"
    },
    "extraResources": [
      {
        "from": "./bin",
        "to": "bin",
        "filter": [ "**/*" ]
      }
    ],
    "files": [
      {
        "from": "./ElectronHostHook/node_modules",
        "to": "ElectronHostHook/node_modules",
        "filter": [ "**/*" ]
      },
      "**/*"
    ],
    "linux": {
      "target": ["AppImage"],
      "category": "Science",
      "publish": ["github"]
    },
    "appImage": 
    {
      "artifactName": "RaspberrySour.AppImage"
    }
  },
  "publish": [{
    "provider": "github",
    "owner": "stonkie",
    "repo" : "RaspberrySour",
    "publishAutoUpdate": true,
    "releaseType": "prerelease",
    "url" : "https://github.com/stonkie/RaspberrySour.git",
    "private": false
  }]
}

Relevant logs.

Originally created by @stonkie on GitHub (Jul 13, 2020). I used electron.net to build a Blazor sample that runs on a Raspberry Pi. I automated the CI/CD pipeline using AWS CodeBuild. Everything works fine and my artifacts are correctly available through S3, but I cannot get electron-builder to publish to github. It keeps trying to publish to Electron.Net's github repository which is configured in the package.json file although I configured the correct repository in electron.manifest.json . I believe the electron-builder's documentation is clear that it will always do this (so the repo field is not changeable from electron.manifest.json, but that leaves no way to use github publishing with electron.net . Would it make sense for electron.net to support some way of configuring the package.json or is this more of an electron-builder issue? electron.manifest.json { "executable": "RaspberrySour", "splashscreen": { "imageFile": "" }, "name": "RaspberrySour", "author": "Kevin Coulombe", "singleInstance": true, "environment": "Production", "build": { "appId": "com.stonkie.RaspberrySour", "productName": "RaspberrySour", "copyright": "Copyright © 2020 ${author}", "buildVersion": "0.0.5-dev", "compression": "maximum", "directories": { "output": "../../../bin/package" }, "extraResources": [ { "from": "./bin", "to": "bin", "filter": [ "**/*" ] } ], "files": [ { "from": "./ElectronHostHook/node_modules", "to": "ElectronHostHook/node_modules", "filter": [ "**/*" ] }, "**/*" ], "linux": { "target": ["AppImage"], "category": "Science", "publish": ["github"] }, "appImage": { "artifactName": "RaspberrySour.AppImage" } }, "publish": [{ "provider": "github", "owner": "stonkie", "repo" : "RaspberrySour", "publishAutoUpdate": true, "releaseType": "prerelease", "url" : "https://github.com/stonkie/RaspberrySour.git", "private": false }] } Relevant logs. ![image](https://user-images.githubusercontent.com/4596002/87260172-386fdd00-c47e-11ea-863a-3c44a2c17784.png)

claunia added the Feature label 2026-01-29 16:42:10 +00:00

claunia closed this issue

2026-01-29 16:42:11 +00:00

claunia commented

2026-01-29 16:42:11 +00:00

@kieransouth commented on GitHub (Oct 14, 2021):

Yep, this would be great to have.

@kieransouth commented on GitHub (Oct 14, 2021): Yep, this would be great to have.

claunia commented

2026-01-29 16:42:12 +00:00

@FlorianRappl commented on GitHub (Nov 7, 2025):

I think this should just work with the current version.