I attempted to update to 6.2 this morning on my dev server but ran into an issue with dates. I have some dates from a 3rd party that come over with a UTC offset (IE: “March, 07 2026 172937 -0500”. Prior to 6.2 I could parse this with DateConvert(‘utc2Local’, ‘March, 07 2026 172937 -0500’), but now throws an error stating it’s not a valid date. The only way I can get dateconvert() to work now is by dropping the “-0500", then it will work. If I have to pre-parse those strings, i’ll make it happen, just wondering if this is a known thing that I missed here.

Wasn't that listed as breaking change going to 6.0?

Not sure.. I know I’ve been running 6.0.4.10 for a while now without issue.

https://dev.lucee.org/t/cant-cast-march-04-2025-0938-0800-to-date-value/14778 Links to the tickets and prior posts in that discussion.

OK.. Cool, thanks for the heads up!

Try the latest 6.2.1 SNAPSHOT, that regression was addressed yesterday