Hey @Łukasz it's because any fixes which are important are backported to older spark versions in DBR, that's the reason you see this fixed in DBR 13.1

Thanks,
Saikrishna Pujari
Sr. Spark Technical Solutions Engineer, Databricks