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.14.0 : Sets, Ranges, Inner Classes, and a Runtime That Talks Back

BoxLang 1.14.0 : Sets, Ranges, Inner Classes, and a Runtime That Talks Back

BoxLang has never stood still, but 1.14.0 is something different. This is the release where the language stops filling gaps and starts defining what a modern dynamic JVM language looks like on its own terms. Sixty-five issues closed. Four innovative language features. A formatter that has grown up. And a companion module - bx-mcp - that fundamentally changes how you operate a running BoxLang application with AI.

Luis Majano
Luis Majano
June 03, 2026
BoxLang Image Module 1.7.0: Full Format Freedom with WebP, GIF, BMP, TIFF and Built-in CAPTCHA

BoxLang Image Module 1.7.0: Full Format Freedom with WebP, GIF, BMP, TIFF and Built-in CAPTCHA

The BoxLang image module just landed two back-to-back releases that make it significantly more capable. 1.6.0 brought CAPTCHA generation. 1.7.0 adds four new image formats, fixes a silent write bug that has been producing PNG files regardless of what extension you asked for, and adds proper alpha channel handling for formats that don't support transparency. Let's dig in. 🚀

Luis Majano
Luis Majano
June 01, 2026
🚀 Introducing BoxLang MCP: Give Your AI a Window Into Your Running BoxLang Application

🚀 Introducing BoxLang MCP: Give Your AI a Window Into Your Running BoxLang Application

You launch your BoxLang application, traffic flows, schedulers execute, caches warm, threads spin. And when something goes wrong, you jump between logs, dashboards, admin panels, and monitoring tools to piece together the full picture. Meanwhile, your AI coding assistant only understands your source code. It has no visibility into your running application. It cannot tell you why your thread pool is saturated, whether cache performance is degrading, or which scheduled task silently failed overnight.

Luis Majano
Luis Majano
June 01, 2026