configurable package.json path for node releases #2469
Labels
priority: p3
Desirable enhancement or fix. May not be included in next release.
type: feature request
‘Nice-to-have’ improvement, new feature or different behavior or design.
Thanks for stopping by to let us know something could be better!
Is your feature request related to a problem? Please describe.
We have a pretty unique monorepo in which we release only one module and all other modules are rolled up to it during the build phase. When we release, we update
./packages/module_1/package.json
. However, release-please modifies the./package.json
file, which causes a difficulty when we generate a release.Describe the solution you'd like
We should be able to use
--version-file
withnode
release strategy so that we can overridepackage.json
path.Describe alternatives you've considered
We have tried to use different strategies instead of node but nothing seems to work.
Additional context
I will be happy to contribute and submit a solution for this.
The text was updated successfully, but these errors were encountered: