Closed pdanpdan closed 3 weeks ago
Neat :+1:
If we break down the commit in two commits, then @brillout/release-me
will correctly update all the CHANGELOG.md
files:
packages/vike-vue
(without fix:
commit message prefix)packages/vike-{vue-query,pinia}
(with fix:
prefix and a second commit message line BREAKING CHANGE:
)After merging, I'll bump and release a new major for vike-{vue-query,pinia}
.
On a tangent @4350pChris and myself where thinking of renaming vike-pinia
to vike-vue-pinia
to keep things consistent. I think we can do this at some point later.
Edit: or three commits if we want a different BREAKING CHANGE:
message.
Sure, it makes sense. Just let me check something about a hydration error in vike-vue-query
before, because I was on it.
can you please check if it looks ok as it is split now?
Yes, LGTM. Can I merge & release?
You can merge. For release should we also change the name of the package first?
For release should we also change the name of the package first?
As you wish.
@4350pChris WDYT?
Maybe it would be nice to do it, so we have it behind us ✅
Go ahead and change it 👍
vike-vue-query@0.0.3
released.
I wonder why the CI wasn't triggered for this PR :thinking:
I was under the impression the following would work: https://github.com/vikejs/vike-vue/blob/b3c0cb2df9d4e30540315dc36d9a73026a243fbc/.github/workflows/ci.yml#L2-L7
I wonder why the CI wasn't triggered for this PR 🤔
Nevermind, it seems to be working: https://github.com/vikejs/vike-vue/pull/94.
close #92