v2.2.10

[KazariEX]

Pick the 4 fixes after 2.2.8 (including the important #5247).

[pkg-pr-new]

Open in StackBlitz

vue-component-meta

npm i https://pkg.pr.new/vuejs/language-tools/vue-component-meta@5332

vue-component-type-helpers

npm i https://pkg.pr.new/vuejs/language-tools/vue-component-type-helpers@5332

@vue/language-plugin-pug

npm i https://pkg.pr.new/vuejs/language-tools/@vue/language-plugin-pug@5332

@vue/language-core

npm i https://pkg.pr.new/vuejs/language-tools/@vue/language-core@5332

@vue/language-server

npm i https://pkg.pr.new/vuejs/language-tools/@vue/language-server@5332

@vue/language-service

npm i https://pkg.pr.new/vuejs/language-tools/@vue/language-service@5332

vue-tsc

npm i https://pkg.pr.new/vuejs/language-tools/vue-tsc@5332

@vue/typescript-plugin

npm i https://pkg.pr.new/vuejs/language-tools/@vue/typescript-plugin@5332

commit: 424e937

[RayGuo-ergou]

Hi @KazariEX could we do release with version tags as some eco system CIs relies on the tags, e.g. https://github.com/mason-org/mason-registry/actions/runs/14600381065/job/40956852445?pr=9781 failed because was checking https://raw.githubusercontent.com/vuejs/language-tools/v2.2.10/extensions/vscode/package.json which does not exist.

Might because here https://github.com/vuejs/language-tools/blob/master/package.json#L11 explicitly set to no tag version 🤔? Not sure if this is a good idea tho.

[KazariEX]

It seems that tag cannot be set on branches. I thought rebasing the release commit to the main branch may cause confusion between versions.

[RayGuo-ergou]

oh okay makes sense thanks

[RayGuo-ergou]

but isn't tags on commits not branches? So as long as you give the correct hash of the commit to create the hash should be fine?

but anyway not a big deal if not release none default branches now.

[KazariEX]

Added.