We are pleased to announce the general availability of CommandBox 6.3.0.  This minor release has a handful of bug fixes and some new features.  You can check out the latest documentation here:

https://commandbox.ortusbooks.com/

You can download the latest version here:

https://www.ortussolutions.com/products/commandbox#download

or by running the "upgrade" command from within your CLI. The new version will also come with the latest versions of bundled modules.

What's New 🚀

Here's an overview of the new goodies in this release.

box-lock.json Package Lock File

This release introduces lock file support for CommandBox package management, ensuring consistent dependency versions across installations. When you use the new --lock flag with the install command, CommandBox creates a box-lock.json file that pins exact versions of your dependencies. The system intelligently maintains these locked versions during install, uninstall, and update operations while respecting your semver ranges—automatically updating the lock file when your requested version falls outside the locked range or when using force installs. This feature works seamlessly alongside existing workflows and has no impact on projects that don't use lock files.

install --lock

package link BoxLang modules

When developing on BoxLang modules, you can now use the package link command to symlink those modules to your BoxLang home's modules folder.

package link ~/.boxlang/modules

Override Module settings with env vars

This didn't work in the past due to chicken/egg issues and the order things loaded.  Now you can use global env vars to override how modules behave, which is nice for CI environments.

box_config_modules_moduleName_settingName=value

STOMP/Websocket heartbeat improvement

After some real-world testing with our STOMP/Websocket implementation, we've enhanced STOMP heartbeats to be replied to directly from Undertow/Java without hitting your CF code. This improves performance and removes clutter in your performance profiling tools.

Server Process Working Directory

When starting a server, the Java server process will be the directory that the server.json lives in, otherwise the web root.  This affects how Java's default behavior of expanding relative paths works, and allows you to use the user.dir java system property in your config files for relative paths.

BoxLang-aware rewrites

The default rewrite rule will automatically use index.bxm instead of index.cfm when you start a BoxLang server which has an index.bxm file in the web root.  You can now also override the front controller with a custom server rule.

framework-rewrite( 'myFrontController.bxm' )

Updated Dependencies

We've also updated to the latest Undertow and Lucee libraries.  Note this Undertow update includes some security fixes from RedHat.

Release Notes ⚡️

Here are the full release notes for this release.