BREAKING CHANGE: The type of `defineComponent()` when passing in a function has changed. This overload signature is rarely used in practice and the breakage will be minimal, so repurposing it to something more useful should be worth it.
close#3102
- No longer implicitly register global JSX types by default
- This avoid conflict when using Vue in the same project with React
- Global registration must now be done by explicitly importing /
referencing `vue/jsx`, or listing it in `compilerOptions.types`.
- Add `vue/jsx-runtime` to support `jsxImportSource` usage
- Can enable globally by setting `compilerOptions.jsxImportSource` to `'vue'`
- Can also opt-in per-file with `/** @jsxImportSource vue */`
* build: support `--canary` flag for canary releases
Also adds `--skip-git` and `--skip-prompts` flags as they would be
useful in ecosystem-ci
* ci: add a workflow to do canary releases every Monday
* build: allow manually releasing patch canary versions
* chore: don't bother updating the README
As far as I know, only Knighly modifies the README for nightly builds:
<https://www.npmjs.com/package/@knightly/vue>
Nuxt, React, and TypeScript all keep the README as-is for edge releases.
So I think we can avoid the complexity here.
* refactor: checkCIStatus -> getCIResult
* chore: keep the canary major in sync with the repo major
* fix: fix version rewriting
* fix: `@vue/compat` is also a core package
The directory name format of `@vue/compat` is different from other core packages, so it needs to be handled separately.
Missing it didn't cause any problems because the `isCorePackage`
function is only used to test dependency names, and `@vue/compat` isn't
used as a dependency anywhere.
But it's good to fix it anyway.
Evan You