Version Packages

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.

Releases

eslint-plugin-vue@10.7.0

Minor Changes

• Added new -error config variants, with all rules' severity set to error: strongly-recommended-error, recommended-error, vue2-strongly-recommended-error, vue2-recommended-error (along with their flat config equivalents) (#2796)

• Added new vue/no-literals-in-template rule (#3000)

• Added new vue/no-undef-directives rule (#2990)

• Added TypeScript support for eslint-plugin-vue development (#2916)

• Changed vue/no-negated-v-if-condition suggestion to autofix (#2984)

• Added new ignoreEOLComments option to vue/no-multi-spaces rule (#2989)

Patch Changes

• Updated Vue 3 export names resources: added DirectiveModifiers (#2996)

• Updated Vue 3 export names resources: added nodeOps and patchProp (#2986)

• Fixed false positives in vue/define-props-destructuring rule when imported types are passed to defineProps (#2995)

[thor-juhasz]

@FloEdelmann
Sorry for pinging you if the wrong person.

Note that the docs website is reflecting changes introduced in this PR

Here: https://eslint.vuejs.org/user-guide/

I see the "Alternatively, there are versions of the configs with all rules set to error suffixed with -error that you can use." statement (implemented in #2796) which I was happy to see. But alas, it's not actually released yet.

Is the workflow mistakenly publishing there?

And when will this actually get released? Is there some schedule?

[FloEdelmann]

docs website is reflecting changes introduced in this PR
[…]
Is the workflow mistakenly publishing there?

No, it works as intended. But we can think about deploying the docs only after a release, and have the master branch docs on a subdomain or similar. @thor-juhasz could you please open a new issue for that, so that it can be properly discussed?

And when will this actually get released? Is there some schedule?

No, we release a patch version relatively quickly if there are critical bugs, and a minor version when enough stuff has accumulated and not too many work-in-progress PRs are open. But we'll likely release soon™.