Skip GitHub releases for dependency-only updates in a monorepo? #2419
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'm using the manifest releaser along with the node-workspaces plugin in a monorepo with 40-odd packages.
During the release process, any sibling packages in the monorepo that depend on each other have that dependency updated when the sibling changes, a git tag is created for the release and the new version is published to npm, which is what we want.
Is it possible to configure skipping the creation of a GitHub release for a monorepo package release when all that release contains is dependency updates?
The reason is the GitHub releases page becomes totally unusable - the documentation for what features/bug fixes are contained in a release of one monorepo package is buried under loads of releases that are just reporting patch updates of monorepo sibling deps.
The text was updated successfully, but these errors were encountered: