The commits to 1.24 and 1.25 match the tested and blessed revisions in CI, these branches are fix committed.
http://reports.vapour.ws/releases/issue/5604a1a7749a561f57c47dc4 shows that master did not have this issue at the time of the bug report, but on Friday Oct 2, it appears and is a cause of failure for 3 builds, so the bad behaviour was eventually merged into master and no needs fixing.
The commits to 1.24 and 1.25 match the tested and blessed revisions in CI, these branches are fix committed.
http:// reports. vapour. ws/releases/ issue/5604a1a77 49a561f57c47dc4 shows that master did not have this issue at the time of the bug report, but on Friday Oct 2, it appears and is a cause of failure for 3 builds, so the bad behaviour was eventually merged into master and no needs fixing.