Where do i specifiy "githubArtifactName" within package.json?
See original GitHub issue- Version: 15.6.2
- Target: win32
None of the locations i tried (within package.json
) lets me add a custom githubArtifactName
(or any properties from latest.yml
, like path
), my config never passes validation.
Where can i add these custom versionInfo
properties?
my package.json
...
},
"build": {
"win": {
"icon": "./icons/win32/icon.ico",
"target": [
"nsis"
]
},
"nsis": {
"artifactName": "${name}-setup-${version}.${ext}",
"deleteAppDataOnUninstall": true,
"oneClick": false,
"runAfterFinish": false
}
}
...
Thanks, @develar !
Issue Analytics
- State:
- Created 7 years ago
- Comments:10 (8 by maintainers)
Top Results From Across the Web
Job artifacts - GitLab Docs
Create job artifacts · Use CI/CD variables to define the artifacts name · Exclude files from job artifacts · Add untracked files to...
Read more >Jobs artifacts administration - GitLab Docs
The artifacts are stored by default in /home/git/gitlab/shared/artifacts . To change the storage path for example to /mnt/storage/artifacts , edit /home/git/ ...
Read more >Maven packages in the Package Registry - GitLab Docs
Publish Maven artifacts in your project's Package Registry. Then, install the packages whenever you need to use them as a dependency.
Read more >Artifacts Filename Cannot Be Set with Dynamic Variables
The script above results in an artifacts file like that: MyName_.zip but desired is MyName_SomeVal.zip. Why is this desired?
Read more >npm packages in the Package Registry - GitLab Docs
Create or edit the .npmrc file in the same directory as your package.json in a GitLab project. Include the following lines in the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
In the 16.2.0 case fixed.
@krystophv … because file name contains build version, but not build number.
Well, maybe it is better to use different product name? Ook. It seems issue should be reopened.