These rules are currently in configs for Vue 2 (in all ofessential,strongly-recommended andrecommended), but not in configs for Vue 3:

• vue/no-custom-modifiers-on-v-model
  → could be useful as an uncategorized rule for Vue 3 to disallowcustom modifiers, so let's not deprecate it
• vue/no-multiple-template-root
  → could be useful as an uncategorized rule for Vue 3 to preventattribute inheritance problems, so let's not deprecate it
• vue/no-v-for-template-key
  → makes no sense for Vue 3, so deprecate it (seeVue 3 Migration Guide:key Attribute)
• vue/no-v-model-argument
  → makes no sense for Vue 3, so deprecate it (seeVue 3 Migration Guide:v-model)
• vue/valid-model-definition
  → makes no sense for Vue 3, so deprecate it (seeVue 3 Migration Guide:v-model)
• vue/valid-v-bind-sync
  → makes no sense for Vue 3, so deprecate it (seeVue 3 Migration Guide:v-model)

I didn't find anyuncategorized rules that would only be useful for Vue 2.

Thus, deprecating them is not technically a breaking change, but I think it will receive more attention if we do it in a major version.