We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
package.json
I'm trying to inject app version on compile stage. I have a package.json with major.minor version part and compile app like so:
major.minor
electron-builder build -c.extraMetadata.version=$MAJOR.$MINOR.$DYNAMICALLY_CALCULATED_PATCH
The final command may look like this:
electron-builder build --config electron-builder.mjs --publish never -c.extraMetadata.version=3.1.1731434857-vanilla-ts
But it fails with error:
Invalid version: "3.1" failedTask=build stackTrace=Error: Invalid version: "3.1"
As I assume, version checking happens before all injections into the package.json
The text was updated successfully, but these errors were encountered:
Curious, why not just set the package.json version to major.minor.0? Your c.extraMetadata.version will override it anyways later on
major.minor.0
c.extraMetadata.version
Sorry, something went wrong.
Yeap. I can do that. But It's just not intuitive. If I inject the version, I expect it to be validated.
No branches or pull requests
I'm trying to inject app version on compile stage. I have a
package.json
withmajor.minor
version part and compile app like so:The final command may look like this:
But it fails with error:
As I assume, version checking happens before all injections into the package.json
The text was updated successfully, but these errors were encountered: