Yesterday, I upgraded from 0.101.0 to 0.102.0 and date to-table was replaced equally (actually better) with intorecord, however it was not documented well in the error. Had to research for 5 to 10 minutes, which does not sound much, but if you get this like every second version, the amount of time adds up quickly.
Actually had been deprecated beforehand, you should have gotten a warning. The deprecation cycle certainly is quite short, I’m still on 0.100.0, If I were to upgrade now I’d jump the version with the warning.
Yes, I switched to an older version and there was the warning. However, there was no warning on 0.101.0 whatsoever, so upgrading just one patch version broke my master module.
Sometimes, I skip some versions, so I am certain, that I jumped from < 0.100.0 straight to 0.101.0 and here we are, without any deprecation warning.
Yesterday, I upgraded from
0.101.0to0.102.0anddate to-tablewas replaced equally (actually better) withinto record, however it was not documented well in the error. Had to research for 5 to 10 minutes, which does not sound much, but if you get this like every second version, the amount of time adds up quickly.Actually had been deprecated beforehand, you should have gotten a warning. The deprecation cycle certainly is quite short, I’m still on 0.100.0, If I were to upgrade now I’d jump the version with the warning.
Yes, I switched to an older version and there was the warning. However, there was no warning on
0.101.0whatsoever, so upgrading just one patch version broke my master module.Sometimes, I skip some versions, so I am certain, that I jumped from <
0.100.0straight to0.101.0and here we are, without any deprecation warning.