-
Notifications
You must be signed in to change notification settings - Fork 19.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: merge next
branch into master
#18786
Conversation
… only when direction is 'nodirection'
chore: merge 'master' branch into 'next'
Merge branch 'master' into 'next'
feat: multiple level drill down support for universalTransition
Merge branch 'master' into 'next'
chore: merge master to next
chore: merge `master` branch to `next` branch to fix broken nightly-next build
Thanks for your contribution! The pull request is marked to be To reviewers: If this PR is going to be described in the changelog in the future release, please make sure this PR has one of the following labels: This message is shown because the PR description doesn't contain the document related template. |
The next version may not be 5.5.0. If there aren't enough major features, we may still release 5.4.3. So perhaps we should wait until we decide if we should release 5.5.0 as the next version? |
@Ovilia Looked through the merged pull requests, the most are to fix bugs. I have no objection to releasing v5.4.3 instead of v5.5.0. |
Let's create a milestone for v5.4.3 and move the pull requests and issues to it. |
@plainheart Do you think it could be 5.5.0 if I can complete the SSR client runtime before the next release? I'm working on the building scripts and should be ready in a few days. |
@plainheart Sure. Let's start the release of 5.4.3 soon. Should this PR be closed for now or turn it into draft? |
@Ovilia I've listed it in v5.5.0. Just leave it alone until v5.5.0 is ready to release. |
Congratulations! Your PR has been merged. Thanks for your contribution! 👍 |
Thank you all for reviewing and testing the PR and really excited to see the minor work being merged into |
Brief Information
This pull request is in the type of:
What does this PR do?
Current
next
branch contains a PR #17611 that should be included in v5.5.0.