Blog

CommandBox 4.1.0 Released

Brad Wood June 26, 2018

Spread the word

Brad Wood

June 26, 2018

Spread the word


Share your thoughts

Close on the heels of our big CommandBox 4.0.0 release, we have a small update we've released today: 4.1.0.  This release is mostly to fix a couple small bugs in the 4.0.0 release, but it does have a few new features in it, so we've bumped a full minor version instead of just a patch release.

The download page, apt/yum repos, and Homebrew have all been updated with the new release.  Here's a few highlights:

Release Highlights

  • Fixed the annoying "server spanner" error that *nix users saw when starting servers.
  • Updated CLI engine (and default server) version to Lucee 5.2.7.63 which includes an important security fix.
  • Added a new "noninteractive" setting to improve the output on build servers like Jenkins or Travis-CI
  • Task runner metadata changes picked up without needing to reload the CLI
  • Ability to load ad-hoc modules on the fly from Task Runners

Release Notes

Here's the full list of tickets we addressed in the 4.1.0 release.  Thanks to those who send me pull requests for some of these fixes and features!

Bug

New Feature

  • [COMMANDBOX-669] - Localized CommandBox Modules
  • [COMMANDBOX-793] - Add new slugify function to the formatter utility
  • [COMMANDBOX-794] - When creating coldbox skeleton apps, clear out the basic name, slug, version, location and scripts so the user can configure them
  • [COMMANDBOX-797] - Added new bundles,labels,verbose,directory arguments to the testbox watch command to allow for granular executions
  • [COMMANDBOX-798] - Added verbose options to passthrough to the testbox runner so it true it can return the debug buffer

Improvement

  • [COMMANDBOX-792] - Remove legacy installColdbox, installColdboxBE, installTestbox arguments from create commands
  • [COMMANDBOX-796] - Added ability to visualize the exception stacktraces with a configurable depth.
  • [COMMANDBOX-800] - Add setting to force "non interactive" shell that disables fancypants progress output
  • [COMMANDBOX-803] - Change user agent on downloader to get around proxies like cloudflare
  • [COMMANDBOX-804] - Store less "result" text in CommandBox's servers.json
  • [COMMANDBOX-807] - Upgrade core Lucee engine to 5.2.7.63

Add Your Comment

Recent Entries

BoxLang 1.17 Series Part 3 : Encrypted Config Secrets

BoxLang 1.17 Series Part 3 : Encrypted Config Secrets

Everyone knows the datasource password should not be sitting in plain text in a config file. Everyone has also, at some point, shipped exactly that, because the alternative was a pile of environment variable plumbing that nobody wanted to build on a deadline. x

Luis Majano
Luis Majano
September 08, 2026
BoxLang AI 3.4 Blog Series Part 3 : Batched Approvals

BoxLang AI 3.4 Blog Series Part 3 : Batched Approvals

Here's a bug that's easy to miss until it bites someone in production: an agent turn asks for two tool calls at once, both need human approval, and only the first one actually suspends. The second one gets silently skipped. Not rejected, not queued, just gone. That's what happened before 3.4.0, and it's fixed now with batched tool-call approvals.

Luis Majano
Luis Majano
September 08, 2026
Getting Started with BoxLang as an Alternative CFML Engine

Getting Started with BoxLang as an Alternative CFML Engine

If you have an existing ColdFusion or Lucee application, one of the first questions you may have about BoxLang is probably not:

“Should I rewrite my application in BoxLang?”

It is much simpler:

“Can BoxLang run the CFML application I already have?”

That was the focus of veteran CFML troubleshooter Charlie Arehart’s session at Into the Box 2026, Getting Started with BoxLang as an Alternative CFML Engine.

Cristobal Escobar
Cristobal Escobar
September 08, 2026