Problem

When specifying a package name or glob expression in the ignore config option that doesn't match any workspace package, changesets throws a validation error:

The package or glob expression "generated-package-*" is specified in the `ignore` option but it is not found in the project.

This makes it impossible to use ignore patterns for packages that may not always be present, such as:

• Dynamically generated packages (e.g. Prisma client packages that only exist after prisma generate)
• Conditionally installed packages (present in some environments but not others)
• Future packages not yet created but already listed in config

Solution

Remove the unmatched-pattern validation for the ignore option. Unlike fixed and linked groups — where all packages must exist to form a valid constraint group — ignoring a non-existent package is a safe no-op: the pattern simply matches nothing and has no effect on the release plan.

The fixed and linked group validations are unchanged, since those do require all referenced packages to exist.

Changes

• Removes the unmatched-pattern error check in @changesets/config
• Updates tests: the two tests that previously expected errors for non-existent ignore packages now verify the config parses successfully with an empty ignore array

Related

Closes #1794