Closed shairez closed 4 days ago
Latest commit: 6242382ac0a6fbf01786f56623d8c4c697f5457a
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
npm i https://pkg.pr.new/@builder.io/qwik@7064
npm i https://pkg.pr.new/@builder.io/qwik-city@7064
npm i https://pkg.pr.new/eslint-plugin-qwik@7064
npm i https://pkg.pr.new/create-qwik@7064
commit: 831c84b
Name | Status | Preview | Last Commit |
---|---|---|---|
qwik-docs | ✅ Ready (View Log) | Visit Preview | 831c84b365d9ee58677e135ede9803a003ec2cb1 |
What is it?
Description
We want to make sure that we release only versions that have been tested by our "alpha testers" team.
Currently, releasing from
main
is problematic, because PRs might get merged between the time we got a 👍 from the testers but before we release, meaing bugs can creep in.Having a pure
upcoming
release branch, where everything is being tested from allows us to release fully tested and more stable versions.The new flow will be:
PRs are merged into
main
main
is periodically merged intoupcoming
A new
Versions
PR is getting created automatically by changesets against theupcoming
branch (instead ofmain
).When we are ready to cut a release, we ask the alpha testers to test the
pkg.pr.new
version from theupcoming
branch.After we get the approval that the new version on is checked and verified to be working with multiple projects, we can merge the
Vesions
PR into theupcoming
branch which will kick off the auto release process.After the release we merge
upcoming
intomain
so it'll have the latest released version numbers.Checklist