We have a monorepo of packages and want to use the "ignore" option to skip versioning and publishing a package temporarily.

The initial run of the workflow correctly runs the version, which respects the ignore option and only consumes, bumps version, and updates changelog for packages not ignored.

However, the subsequent run of the workflow still detects the leftover changeset markdown files of the ignored package, i.e. hasChangesets is true and tries to run the version again. If the detected changesets are all for ignored packages, hasChangesets should be set to false and enter the publish flow.

From what I can tell, the "ignore" option is only read and considered in @changesets/assemble-release-plan.

Instead of just reading all changesets below,