Bump to version 2.0.0

[stockiNail]

No description provided.

[stockiNail]

I have seen a warning from Vue-Press:

[@vue/compiler-sfc] ::v-deep usage as a combinator has been deprecated. Use :deep(<inner-selector>) instead.

The warnings sound to be related to @simonbrunel/vuepress-plugin-versions (file /src/components/VersionsDropdown.vue) and vuepress-theme-chartjs(file /components/Tooltip.vue)

Edit:
Opened 2 issues:

• ::v-deep usage as a combinator has been deprecated simonbrunel/vuepress-theme-chartjs#3
• ::v-deep usage as a combinator has been deprecated simonbrunel/vuepress-plugin-versions#1

[stockiNail]

I have seen a warning from Vue-Press:

[@vue/compiler-sfc] ::v-deep usage as a combinator has been deprecated. Use :deep(<inner-selector>) instead.

Shall we wait for fix in the other projects?

[LeeLenaleee]

What if you just upp the version number and not the versions of the used packages

[stockiNail]

What if you just upp the version number and not the versions of the used packages

It works. I rollback the the package-lock.json.

[stockiNail]

I don't see any npm deployment and also the version is still in draft... Is it usual?

[kurkle]

Yes, you need to publish that release, which will trigger the npm publish.

[stockiNail]

oh... I was convinced that last time it was done automatically. I put it in my notes.

Thank you @kurkle

[LeeLenaleee]

@stockiNail you are not the only one, if you wanna know how to publish (took me some googling) go to the draft click the pencil on the top right to edit it then at the bottom you have a big green publish button

[stockiNail]

@stockiNail you are not the only one, if you wanna know how to publish (took me some googling) go to the draft click the pencil on the top right to edit it then at the bottom you have a big green publish button

Thank you @LeeLenaleee !!! I know how to do it manually, having other projects where I'm doing that but I was convinced (dont ask me why) here it was all automated, triggered by Bump PR. And I was wondering how the deployment could start based on event of a merged specific PR.... Now it's clear! ;)