The release PR is created by github-actions instead of our bot, which means it can create the PR on a branch inside the repo. However, since it's triggered from a workflow with the default GITHUB_TOKEN, additional checks won't be run. Since we require base branches to be up-to-date before merging and require CI to pass before merging, constantly running tests on each merge for both the dist build and the release PR wastes a lot of resources.
If needed, we can always close and re-open the PR to force the tests to run before we actually merge.
The release action maintains a floating tag alias for the latest major version.
The release PR is created by github-actions instead of our bot, which means it can create the PR on a branch inside the repo. However, since it's triggered from a workflow with the default GITHUB_TOKEN, additional checks won't be run. Since we require base branches to be up-to-date before merging and require CI to pass before merging, constantly running tests on each merge for both the dist build and the release PR wastes a lot of resources.
If needed, we can always close and re-open the PR to force the tests to run before we actually merge.
The release action maintains a floating tag alias for the latest major version.