How does MySQL rotate binary log files when number extension reaches its maximum? Assume the bin-log file format is: something-bin-log.000122. With each file has a maximum of 1GB size before rotating, and with cap on the number of old binary log files - say 14 days.

What will be the next file when the current one is something-bin-log.999999 and it is about to get rotated?

Will the next binary log file be something-bin-log.000001? If so, how to prevent this from happening and use a bigger numeric extension instead?
An error is generated when the numbers run out:

source code reference