vue3-core/scripts
Haoqun Jiang 29852dfa9c
ci: release canary versions every week (#7860)
* 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.
2023-03-17 15:37:29 +08:00
..
aliases.js chore: use type: "module" 2023-02-03 18:12:56 +08:00
build.js build: reuse const enum data between concurrent rollup builds 2023-02-06 09:35:08 +08:00
const-enum.js fix(build): fix const enum w/ number values 2023-02-06 14:03:15 +08:00
dev.js chore: use consistent ts-check comments in scripts 2023-02-03 18:24:03 +08:00
pre-dev-sfc.js chore: use consistent ts-check comments in scripts 2023-02-03 18:24:03 +08:00
preinstall.js chore: use consistent ts-check comments in scripts 2023-02-03 18:24:03 +08:00
release.js ci: release canary versions every week (#7860) 2023-03-17 15:37:29 +08:00
setupVitest.ts wip(vitest-migration): reactivity tests passing 2023-01-26 15:25:55 +08:00
utils.js chore: use consistent ts-check comments in scripts 2023-02-03 18:24:03 +08:00
verifyCommit.js chore: use consistent ts-check comments in scripts 2023-02-03 18:24:03 +08:00