How to not publish certain modules using the manifest releaser #2373
Labels
priority: p3
Desirable enhancement or fix. May not be included in next release.
type: question
Request for information or clarification. Not an issue.
I have a JavaScript monorepo that uses the release-please manifest releaser with the
node-workspace
plugin.A couple of packages are only used internally so don't need to be published.
They have private: true in their
package.json
so they are easy to detect.If I add them to the manifest, e.g.:
..then the release-please action adds the private modules to the
chore: release main
PR with a bumped version number as if it's about to publish them.If I omit them from the manifest, their dependencies on other modules in the monorepo don't get updated which can make CI for the release PR fail, and/or it means I need to go in and manually update the deps after the release has occurred.
Is there a way to get the manifest releaser to update the sibling dependencies of the private modules like the public, to-be-published modules but to not bump their version numbers or publish them?
The text was updated successfully, but these errors were encountered: