generic publisher config does not accept any requestHeaders

• Electron-Builder Version: 22.14.13

• Node Version: 16.14.0

• Electron Version: 17.0.0
• Electron Type (current, beta, nightly): current

• Target: MacOS

Hi Guys,

i am trying to use the generic publisher option in electron-builder, but it seems not to accept any request headers. My publish config in builder.config.js:

module.exports = {
...
    publish: {
        provider: "generic",
        url: "http://localhost:3000/electron_publish",
        requestHeaders: {
            "access-token": "some-access-token-here"
        }
    }
}

If i try to build i just receive an error message:

 - configuration.publish should be one of these:
   object { provider, channel?, host?, owner?, private?, protocol?, publishAutoUpdate?, publisherName?, releaseType?, repo?, requestHeaders?, token?, updaterCacheDirName?, vPrefixedTagName? } | object { bucket, provider, acl?, channel?, encryption?, endpoint?, path?, publishAutoUpdate?, publisherName?, region?, requestHeaders?, storageClass?, updaterCacheDirName? } | object { name, provider, region, acl?, channel?, path?, publishAutoUpdate?, publisherName?, requestHeaders?, updaterCacheDirName? } | object { provider, url, channel?, publishAutoUpdate?, publisherName?, requestHeaders?, updaterCacheDirName?, useMultipleRangeRequest? } | object { provider, component?, distribution?, owner?, package?, publishAutoUpdate?, publisherName?, repo?, requestHeaders?, token?, updaterCacheDirName?, user? } | object { provider, publishAutoUpdate?, publisherName?, requestHeaders?, updateProvider?, updaterCacheDirName?, <key>: {} } | object { account, product, provider, channel?, platform?, publishAutoUpdate?, publisherName?, requestHeaders?, updaterCacheDirName? } | object { provider, channels?, publishAutoUpdate?, publisherName?, repo?, requestHeaders?, updaterCacheDirName? } | object { owner, provider, slug, channel?, publishAutoUpdate?, publisherName?, requestHeaders?, token?, updaterCacheDirName?, username? } | [object { provider, channel?, host?, owner?, private?, protocol?, publishAutoUpdate?, publisherName?, releaseType?, repo?, requestHeaders?, token?, updaterCacheDirName?, vPrefixedTagName? } | object { bucket, provider, acl?, channel?, encryption?, endpoint?, path?, publishAutoUpdate?, publisherName?, region?, requestHeaders?, storageClass?, updaterCacheDirName? } | object { name, provider, region, acl?, channel?, path?, publishAutoUpdate?, publisherName?, requestHeaders?, updaterCacheDirName? } | object { provider, url, channel?, publishAutoUpdate?, publisherName?, requestHeaders?, updaterCacheDirName?, useMultipleRangeRequest? } | object { provider, component?, distribution?, owner?, package?, publishAutoUpdate?, publisherName?, repo?, requestHeaders?, token?, updaterCacheDirName?, user? } | object { provider, publishAutoUpdate?, publisherName?, requestHeaders?, updateProvider?, updaterCacheDirName?, <key>: {} } | object { account, product, provider, channel?, platform?, publishAutoUpdate?, publisherName?, requestHeaders?, updaterCacheDirName? } | object { provider, channels?, publishAutoUpdate?, publisherName?, repo?, requestHeaders?, updaterCacheDirName? } | object { owner, provider, slug, channel?, publishAutoUpdate?, publisherName?, requestHeaders?, token?, updaterCacheDirName?, username? } | string, ...] | null | string
   Details:
    * configuration.publish.requestHeaders has an unknown property 'access-token'. These properties are valid:
      object {}

I guess i am passing the wrong configuration. In this case please tell me how to do it right, because i can not find my mistake related to the documentation.

Thank you very much

[fauxsoup]

Hmmm That’s for configuration/scheme validation, it doesn’t have any application to the rest of the build process. It’s autogenerated. From the commit you linked though, I do see

-    "@types/node": "^14.10.3",
+    "@types/node": "^14.11.2",

Could that be related?

I believe so. Validation is asserting an empty object for request headers, I’m just not sure where the validation rule comes from

[mmaietta]

I force installed via pnpm upgrade @types/node@14.10.3 and then reran pnpm schema and the scheme.json file did not change, so I’m not what changed additionalProperties: false. That being said, I found a way to override it since it as I guess the schema generator is not parsing NodeJS.Dict<number | string | string[]> properly.