Closed phil-opp closed 10 months ago
Closing, no longer needed.
How can I review this? Is there a way to see conflict resolution changes of the merge or rebase from master into next or we're all of those already handled in #446?
This was just a fast-forward merge. So this updates the branch to commit f5c2b06, which is part of #446 (before the changelog updates). You can just do a git diff or git log, there should not be any differences.
Ah, ok that makes sense, thanks!
I just fast-forwarded a few more commits from #446 including the version bump commit, so CI (and the semver check in particular) passes.
Update
next
branch with latest changes frommaster
, using the conflict resolution from #446.This PR allows us to apply more changes to the
next
branch before releasev0.15
. In particular, we plan to merge a change to make the GDT const generic before the release.