You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to inject the package version with electron-builder using the following: electron-builder --publish=never -c.mextraMetadata.version=1.3.0. This works perfectly on both the macos and linux builds, but on the windows build I receive the following:
Run bun deploy:electron -c.extraMetadata.version=1.3.0
bun deploy:electron -c.extraMetadata.version=1.3.0
shell: C:\Program Files\PowerShell\7\pwsh.EXE -command ". '{0}'"
$ electron-builder --publish=never -c .extraMetadata.version=1.3.0
• electron-builder version=[2](https://github.com/bluerobotics/cockpit/actions/runs/11282022986/job/31378628325#step:8:2)5.1.8 os=10.0.20348
⨯ ENOENT: no such file or directory, open 'D:\a\cockpit\cockpit\.extraMetadata.version=1.[3](https://github.com/bluerobotics/cockpit/actions/runs/11282022986/job/31378628325#step:8:3).0' failedTask=build stackTrace=Error: ENOENT: no such file or directory, open 'D:\a\cockpit\cockpit\.extraMetadata.version=1.3.0'
Your command is getting split between the -c and .extraMetadata, so the -c is being interpreted as the --config/-c arg
Not sure what bun is doing, but it looks like it's parsing your cmd line args in a problematic manner.
An alternative route is to use the extraMetadata property in an electron-builder config. The .js/.ts config files can accept process.env vars for instance
I'm trying to inject the package version with electron-builder using the following:
electron-builder --publish=never -c.mextraMetadata.version=1.3.0
. This works perfectly on both the macos and linux builds, but on the windows build I receive the following:This can be directly confirmed here.
Am I using the command wrong or is it a bug?
The text was updated successfully, but these errors were encountered: