[x] I have searched the issues of this repository and believe that this is not a duplicate.
Your Environment
semantic-release-chrome version: 1.1.3
What you did and problem description
I've added semantic-release-chrome to a standard chrome extension package which has various source files that get compiled to a /dist folder via an npm build script.
My goal was to have semantic-release-chrome modify the manifest.json with the new version and then have that commited along with package.json and CHANGELOG.md as part of the final release commit.
What happened
Only the dist folder manifest.json is updated which means CWS will get the new version but not GitHub
Suggested solution
Maybe take an array of paths to update the manifest?
This is a bit tricky since updating and zipping both happen during the prepare step which means there's no chance for another plugin to do anything in beween.
Right now, my work around will be to copy the manifest from dest back to src folder in an exec plugin that comes later.
Issue
Your Environment
semantic-release-chrome
version: 1.1.3What you did and problem description
I've added semantic-release-chrome to a standard chrome extension package which has various source files that get compiled to a
/dist
folder via an npm build script.My goal was to have
semantic-release-chrome
modify the manifest.json with the new version and then have that commited along with package.json and CHANGELOG.md as part of the final release commit.What happened
Only the dist folder manifest.json is updated which means CWS will get the new version but not GitHub
Suggested solution
Maybe take an array of paths to update the manifest? This is a bit tricky since updating and zipping both happen during the prepare step which means there's no chance for another plugin to do anything in beween.
Right now, my work around will be to copy the manifest from dest back to src folder in an exec plugin that comes later.