Also, another suggestion would be to publish the javascript file to bower and npm once released. Would help a lot with package management, and make installation much easier.
The gulp file can also have a task to publish to bower/npm, but I think the proper way to handle this is to separate the client javascript file into its own separate repository, and only publish that one as needed. It may not always be necessary to publish a new js version along with binaries, and sometimes a js update may be necessary without a binary one.
This enhancement has been migrated to https://github.com/qzind/tray/issues/13.
Per https://github.com/qzind/qz-print/issues/126#issuecomment-167620965
More resources: https://gist.github.com/coolaj86/1318304
...
@tresf For automating releases, one idea is to create a gulp file: https://github.com/gulpjs/gulp/blob/master/docs/recipes/automate-release-workflow.md
Also look at: https://github.com/stevemao/conventional-github-releaser
The gulp file can also have a task to publish to bower/npm, but I think the proper way to handle this is to separate the client javascript file into its own separate repository, and only publish that one as needed. It may not always be necessary to publish a new js version along with binaries, and sometimes a js update may be necessary without a binary one.