Adding new fixes isn't really a breaking change necessitating a minor version bump, however we have it categorized as such in our current versioning policy. Somewhat asymmetrically, we allow unsafe fixes to be added in patch releases. The idea was originally that unsafe fixes required opt-in so it was okay to add them in patch releases. In general, I think new fixes should be allowed in any release.

The downside here is that users may need to change their configuration to include new fixes as unfixable on patch releases if they do not want the fix. This goes against the intent to have patch releases be free of configuration changes. However, these fixes are unlikely to be applied in a context without manual review.

If accepted, we should make this change as part of v0.2.0 and respect the current rules until then.