@Bodge-IT As you can see, there are no changed files in this PR. That is right because all the version changes have to be ignored, and there were no other changes in 5.4-dev.

Now there is something special with such empty PRs on GitHub: If you will merge it in the normal way, GitHub will still show the 6.0-dev branch being 2 commits behind the default branch.

So the PR would not have the desired effect that your branch is regarded to be up to date by GitHub.

There are 2 possible solutions:

1. Directly merge the branches in the repo without a PR. That is hardcore and should only be done by 100% experts. I did it like that last time. If you want I can do it again, and this PR can be closed. Just let me know if I shall do that.
2. Just close this PR and wait with the upmerge until we have merged some PRs in the 5.4-dev branch, and then do again a new upmerge PR.

We were looking to clear-up after release, so all good. Closing this PR