chore(deps): update dependency vue to v3.4.21 #1987
Conversation
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
|
❌ @renovate[bot] the
📝 What should I do to fix it?All proposed commits should include a sign-off in their messages, ideally at the end. ❔ Why it is requiredThe Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO, reformatted for readability:
Contributors sign-off that they adhere to these requirements by adding a Git even has a |
renovate
bot
force-pushed
the
renovate/vue-3.x-lockfile
branch
from
6ce078a to
0b26f1f
Compare
|
❌ @renovate[bot] the
📝 What should I do to fix it?All proposed commits should include a sign-off in their messages, ideally at the end. ❔ Why it is requiredThe Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO, reformatted for readability:
Contributors sign-off that they adhere to these requirements by adding a Git even has a |
1 similar comment
|
❌ @renovate[bot] the
📝 What should I do to fix it?All proposed commits should include a sign-off in their messages, ideally at the end. ❔ Why it is requiredThe Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO, reformatted for readability:
Contributors sign-off that they adhere to these requirements by adding a Git even has a |
renovate
bot
force-pushed
the
renovate/vue-3.x-lockfile
branch
from
0b26f1f to
e6abf26
Compare
renovate
bot
changed the title
|
❌ @renovate[bot] the
📝 What should I do to fix it?All proposed commits should include a sign-off in their messages, ideally at the end. ❔ Why it is requiredThe Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO, reformatted for readability:
Contributors sign-off that they adhere to these requirements by adding a Git even has a |
1 similar comment
|
❌ @renovate[bot] the
📝 What should I do to fix it?All proposed commits should include a sign-off in their messages, ideally at the end. ❔ Why it is requiredThe Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO, reformatted for readability:
Contributors sign-off that they adhere to these requirements by adding a Git even has a |
renovate
bot
force-pushed
the
renovate/vue-3.x-lockfile
branch
from
e6abf26 to
8331b90
Compare
|
❌ @renovate[bot] the
📝 What should I do to fix it?All proposed commits should include a sign-off in their messages, ideally at the end. ❔ Why it is requiredThe Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO, reformatted for readability:
Contributors sign-off that they adhere to these requirements by adding a Git even has a |
1 similar comment
|
❌ @renovate[bot] the
📝 What should I do to fix it?All proposed commits should include a sign-off in their messages, ideally at the end. ❔ Why it is requiredThe Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO, reformatted for readability:
Contributors sign-off that they adhere to these requirements by adding a Git even has a |
renovate
bot
force-pushed
the
renovate/vue-3.x-lockfile
branch
from
8331b90 to
220ca2b
Compare
renovate
bot
changed the title
|
❌ @renovate[bot] the
📝 What should I do to fix it?All proposed commits should include a sign-off in their messages, ideally at the end. ❔ Why it is requiredThe Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO, reformatted for readability:
Contributors sign-off that they adhere to these requirements by adding a Git even has a |
1 similar comment
|
❌ @renovate[bot] the
📝 What should I do to fix it?All proposed commits should include a sign-off in their messages, ideally at the end. ❔ Why it is requiredThe Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO, reformatted for readability:
Contributors sign-off that they adhere to these requirements by adding a Git even has a |
renovate
bot
force-pushed
the
renovate/vue-3.x-lockfile
branch
from
220ca2b to
5994f14
Compare
|
❌ @renovate[bot] the
📝 What should I do to fix it?All proposed commits should include a sign-off in their messages, ideally at the end. ❔ Why it is requiredThe Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO, reformatted for readability:
Contributors sign-off that they adhere to these requirements by adding a Git even has a |
1 similar comment
|
❌ @renovate[bot] the
📝 What should I do to fix it?All proposed commits should include a sign-off in their messages, ideally at the end. ❔ Why it is requiredThe Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO, reformatted for readability:
Contributors sign-off that they adhere to these requirements by adding a Git even has a |
renovate
bot
force-pushed
the
renovate/vue-3.x-lockfile
branch
from
5994f14 to
5e98b3d
Compare
|
❌ @renovate[bot] the
📝 What should I do to fix it?All proposed commits should include a sign-off in their messages, ideally at the end. ❔ Why it is requiredThe Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO, reformatted for readability:
Contributors sign-off that they adhere to these requirements by adding a Git even has a |
renovate
bot
force-pushed
the
renovate/vue-3.x-lockfile
branch
from
5e98b3d to
1314b87
Compare
|
❌ @renovate[bot] the
📝 What should I do to fix it?All proposed commits should include a sign-off in their messages, ideally at the end. ❔ Why it is requiredThe Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO, reformatted for readability:
Contributors sign-off that they adhere to these requirements by adding a Git even has a |
This PR contains the following updates:
3.3.10->3.4.21Release Notes
vuejs/core (vue)
v3.4.21Compare Source
Bug Fixes
v3.4.20Compare Source
Bug Fixes
v3.4.19Compare Source
Bug Fixes
Features
Performance Improvements
getType()GC and speed (#10327) (603a1e1)v3.4.18Compare Source
Bug Fixes
v3.4.17Compare Source
Reverts
v3.4.16Compare Source
Bug Fixes
MaybeDirtyrecurse (#10187) (6c7e0bd), closes #10185markRaw(#10289) (2312184), closes #10288Reverts
v3.4.15Compare Source
Bug Fixes
Performance Improvements
v3.4.14Compare Source
Bug Fixes
v3.4.13Compare Source
Bug Fixes
v3.4.12Compare Source
Reverts
v3.4.11Compare Source
Bug Fixes
v3.4.10Compare Source
Bug Fixes
v3.4.9Compare Source
Bug Fixes
v3.4.8Compare Source
Bug Fixes
v3.4.7Compare Source
Bug Fixes
<template>tags (#10034) (923d560)h(#9991) (438a74a)Reverts
v3.4.6Compare Source
Bug Fixes
nulltype for textarea value (#9997) (c379bc2), closes #9904v3.4.5Compare Source
Bug Fixes
v3.4.4Compare Source
Bug Fixes
watchEffect(#9948) (f300a40)Performance Improvements
v3.4.3Compare Source
Bug Fixes
v3.4.2Compare Source
Bug Fixes
v3.4.1Compare Source
Bug Fixes
Features
v3.4.0Compare Source
Potential Actions Needed
To fully leverage new features in 3.4, it is recommended to also update the following dependencies when upgrading to 3.4:
If using TSX with Vue, check actions needed in Removed: Global JSX Namespace.
Make sure you are no longer using any deprecated features (if you are, you should have warnings in the console telling you so). They may have been removed in 3.4.
Features
onceoption to watch (#9034) (a645e7a)usingsyntax (#8786) (5b2bd1d)defineModelsupport local mutation by default, remove local option (f74785b), closes /github.com/vuejs/rfcs/discussions/503#discussioncomment-7566278__VUE_PROD_HYDRATION_MISMATCH_DETAILS__feature flag (#9550) (bc7698d)FunctionalComponent(#8644) (927ab17)AriaAttributestype (#8909) (fd0b6ba)ObjectPluginandFunctionPlugintypes (#8946) (fa4969e), closes #8577DefinePropstype (096ba81)PublicPropstype (#2403) (44135dc)hwith native elements (#9756) (a625376)ComponentInstancetype (#5408) (bfb8565)Performance Improvements
BREAKING CHANGES
Global JSX Registration Removed
Starting in 3.4, Vue no longer registers the global
JSXnamespace by default. This is necessary to avoid global namespace collision with React so that TSX of both libs can co-exist in the same project. This should not affect SFC-only users with latest version of Volar.If you are using TSX, there are two options:
Explicitly set jsxImportSource to
'vue'intsconfig.jsonbefore upgrading to 3.4. You can also opt-in per file by adding a/* @​jsxImportSource vue */comment at the top of the file.If you have code that depends on the presence of the global
JSXnamespace, e.g. usage of types likeJSX.Elementetc., you can retain the exact pre-3.4 global behavior by explicitly referencingvue/jsx, which registers the globalJSXnamespace.Note that this is a type-only breaking change in a minor release, which adheres to our release policy.
Deprecated Features Removed
app.config.unwrapInjectedRefhas been removed. It was deprecated and enabled by default in 3.3. In 3.4 it is no longer possible to disable this behavior.@vnodeXXXevent listeners in templates are now a compiler error instead of a deprecation warning. Use@vue:XXXlisteners instead.v-isdirective has been removed. It was deprecated in 3.3. Use theisattribute withvue:prefix instead.v3.3.13Compare Source
Bug Fixes
v3.3.12Compare Source
Bug Fixes
xmlns:xlinktoSVGAttributes(#9300) (0d61b42), closes #9299shallowReftype error (#9839) (9a57158)v3.3.11Compare Source
Bug Fixes
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.