Lucee 6.1.1 (6.1.1.100-RC) Release Candidate

There is a new Lucee 6.1.1.100-RC release candidate available for testing. Give it a try and share your feedback with us.

What’s New?

This release focuses mainly on bug fixes, along with a few useful enhancements.

Key Enhancements

  • Configuration improvements: You can now update your Lucee configuration by simply dropping a .CFConfig.json file with the changes into the /deploy folder (LDEV-4994). No need to have everything in that file, just your changes.

  • BigDecimal support for better precision: All functions now support BigDecimal, giving you more accurate calculations and allowing you to write more precise code.

Full Changelog

Below is the detailed changelog for the Lucee 6.1.1.100 release candidate, including bug fixes, enhancements, and tasks that were completed:

Bug Fixes

  • LDEV-5107: Fixed an issue where urlDecode no longer handled umlauts in input, breaking compatibility with older Lucee versions.
  • LDEV-5104: Resolved a NullPointerException (NPE) in CookieImpl caused by concurrency issues.
  • LDEV-5102: Optimized QueryLazy behavior to prevent unnecessary data fetching on ResultSet.close().
  • LDEV-5091: Fixed the “preserve case” environment variable setting that wasn’t working.
  • LDEV-5086: Addressed a BigDecimal type and value mismatch in ORM prepared statements.
  • LDEV-5083: Resolved a NoHttpResponseException when an API failed to respond.
  • LDEV-5080: Fixed compiling conflicts between threads under load.
  • LDEV-5077: Resolved a socket timeout error: com.jcraft.jsch.JSchException: socket is not established.
  • LDEV-5073: Corrected changes in ParseDateTime parsing behavior between Lucee versions.
  • LDEV-5068: Fixed an invalid URL in the releases.
  • LDEV-5055: Corrected incorrect cf_template_path and path_translated in debugging logs.
  • LDEV-5054: Resolved an issue where changing debug settings would purge the debugging logs.
  • LDEV-5052: Fixed CFConfig import not supporting settings like CacheDefaultQuery.
  • LDEV-5048: Removed unnecessary fields being added during mapping.
  • LDEV-5046: Added missing documentation for cfcomponent accessors and interfaces.
  • LDEV-5045: Added missing documentation for cffunction REST arguments.
  • LDEV-5038: Resolved an issue with truncated class files.
  • LDEV-5035: Fixed an issue where a query with dbtype="query" was running against the default datasource instead of the intended one.
  • LDEV-5034: Fixed a failure in setMode when using extract("tgz") due to directory mask issues on Linux.
  • LDEV-5029: Fixed archives not working when no CFML source is available.
  • LDEV-5023: Resolved concurrency errors in Query of Queries (QoQ) with HSQLDB.
  • LDEV-5013: Improved request throughput performance compared to Lucee 6.0.3.1.
  • LDEV-5010: Improved exception handling for invalid charset errors during fileWrite.

Enhancements

  • LDEV-4994: Added support for deploying .CFConfig.json files via the /deploy folder for configuration updates.
  • LDEV-4990: Improved how log arguments are stored for better readability.
  • LDEV-5089: Switched all functions from double to Number for enhanced precision.
  • LDEV-5081: Removed unnecessary CFML files from bundled archives.
  • LDEV-5070: Reduced the dependency on .CFConfig for configuration management.

Try out this release candidate and let us know how it works for you!

14 Likes

I’ve run a few of our projects with unit and selenium tests under a docker 6.1.1.100-RC container and did not run into any show stoppers. So far so good.

4 Likes

Found one issue, but it was introduced a while ago : Allow dots in datasource names again by tomchiverton · Pull Request #2424 · lucee/Lucee · GitHub

All functions now support BigDecimal

Does this now include cfloop with non-integer “step” attributes? Because I posted awhile back how those were still clearly using double, when they ought to now be using BigDecimal. See my prior post here for details:

Also, NumberFormat() has a serious bug pertaining to BigDecimal (but it also happens on doubles too), which I reported here:

Why still version 6.1.1.1? I’m running 6.2.0.149-SNAPSHOT and it runs stable. (apart from the PDF generating issues)
Why is the RC so behind the snapshots?

1 Like