All commits pushed to main trigger an automatic release
Maintainers can trigger a release by commenting /pkg-pr-new in a PR
This will make testing PRs like https://github.com/stackblitz/tutorialkit/pull/270 a lot easier. In that PR we need to verify that packages are resolved correctly in real environments. Testing such changes by linking packages with file:// or link:// protocols in package.json doesn't provide good confidence - using real published packages is better.
main
trigger an automatic release/pkg-pr-new
in a PRThis will make testing PRs like https://github.com/stackblitz/tutorialkit/pull/270 a lot easier. In that PR we need to verify that packages are resolved correctly in real environments. Testing such changes by linking packages with
file://
orlink://
protocols inpackage.json
doesn't provide good confidence - using real published packages is better.I've used the workflow from Vite as reference: https://github.com/vitejs/vite/blob/main/.github/workflows/publish-commit.yml