Of course not. But it makes sense that a bug with a narrower scope is more likely to escape testing, and apparently something that changed between 15.6.1 (released a month ago) and 15.7 (released two days ago) affects the process of upgrading to 26. So whatever code is at fault is probably pretty recent.