fix(deps): update dependency @vue/compat to v3.2.34 #1817
No reviewers
Labels
No Label
area/internal-code
changes requested
confirmed
dependencies
duplicate
good first issue
help wanted
hosting
invalid
kind/bug
kind/feature
question
wontfix
No Milestone
No project
No Assignees
4 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: vikunja/frontend#1817
Loading…
Reference in New Issue
No description provided.
Delete Branch "renovate/vue-compat-3.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
3.2.31
->3.2.34
Release Notes
vuejs/core
v3.2.34
Compare Source
Bug Fixes
export { default } from '...'
(#5937) (73e6523), closes #5935defineComponent
inference toComponent
(#5949) (7c8f457)v3.2.33
Compare Source
Bug Fixes
v3.2.32
Compare Source
Bug Fixes
Configuration
📅 Schedule: 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 Renovate Bot.
Hi renovate!
Thank you for creating a PR!
I've deployed the changes of this PR on a preview environment under this URL: https://1817-renovate-vue-compat-3-x--vikunja-frontend-preview.netlify.app
You can use this url to view the changes live and test them out.
You will need to manually connect this to an api running somehwere. The easiest to use is https://try.vikunja.io/.
Have a nice day!
fix(deps): update dependency @vue/compat to v3.2.32to fix(deps): update dependency @vue/compat to v3.2.336854f7c98e
to6a3db497b9
6a3db497b9
to3266d6f7b7
3266d6f7b7
toafdaed1272
afdaed1272
to89ef23fcd7
89ef23fcd7
to83dfadfc53
83dfadfc53
to960bd07cc1
We should revert to vue@3.2.32. Right now vue and @vue/compat are out of sync.
I think the issue is related to this: https://github.com/SortableJS/vue.draggable.next/issues/138
What do we need Vue compat even for?
I am actually not sure if we still need it.
We might still have some code that relies on compat behavior without knowing.
We could also just remove it and check how that works out 🤷♂️
Removing @vue/compat won't fix the problem though.
I'd say let's give that a try.
960bd07cc1
to8eced59697
8eced59697
to06bf1702d8
06bf1702d8
tof0211a8cb2
f0211a8cb2
toab21c0ea20
ab21c0ea20
to7e947b65b6
fix(deps): update dependency @vue/compat to v3.2.33to fix(deps): update dependency @vue/compat to v3.2.347e947b65b6
to5a5eb0556e
Closing in favor of #1967