You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Due to the branch reorganizations (next became next-abandoned, 2.4.x became default branch for a while, then it became the snapshot of the 2.4.x release) we may miss some commits that were merged into next but not cherry-picked to main (which will became 2.5.0 at cutoff).
Revisit all issues and PRs that are merged or closed and ensure the commits/changes are available on the main branch.
Due to the branch reorganizations (next became next-abandoned, 2.4.x became default branch for a while, then it became the snapshot of the 2.4.x release) we may miss some commits that were merged into next but not cherry-picked to main (which will became 2.5.0 at cutoff).
Revisit all issues and PRs that are merged or closed and ensure the commits/changes are available on the main branch.
Description
Due to the branch reorganizations (
next
becamenext-abandoned
,2.4.x
became default branch for a while, then it became the snapshot of the 2.4.x release) we may miss some commits that were merged intonext
but not cherry-picked to main (which will became 2.5.0 at cutoff).Revisit all issues and PRs that are merged or closed and ensure the commits/changes are available on the
main
branch.Issues and PRs to review
The text was updated successfully, but these errors were encountered: