search

GabeDuarteM / semantic-release-chrome

Set of semantic-release plugins for publishing a Chrome extension release
https://www.npmjs.com/package/semantic-release-chrome
MIT License
43 stars 16 forks source link

No way to update the non-dist version of manifest.json #81

Open melink14 opened 3 years ago

melink14 commented 3 years ago

Issue

Your Environment

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.

ngshiheng commented 3 months ago

hey @gabeduartem, can I ask if you're accepting contributions for this?