Blog

Brad Wood

September 29, 2016

Spread the word


Share your thoughts

We've updated ForgeBox.io to have updated CF Engines for Adobe ColdFusion (Thanks to Jon Clausen) as well as Lucee Server to include some recent security fixes from each as well as some new yet-to-be-released Lucee features.

Here are the new Adobe ColdFusion versions:

  • ColdFusion 10 Update 21 (10.0.21+300068)
  • ColdFusion 11 Update 10 (11.0.10+300066)

Here are the new Lucee Server versions

  • Lucee 4.5 Stable (4.5.3+020)
  • Lucee 5.0 Stable (5.0.0+254)
  • Lucee 5.0 Snapshot (5.0.1-snapshot+067)
  • Lucee 5.1 Beta 2 (5.1.0-beta.2+031)

To be clear, the Lucee 5.1 beta release is also a "snapshot" of sorts but it differs from the 5.0.1 snapshot in that 5.0.1 has fixes and small enhancements to the initial 5.0.0 release.  Lucee 5.1 "beta" will be the next large release of Lucee that contains things like Adobe ColdFusion 2016 compatibility.  The beta channel also gets the same fixes as the 5.0.1 snapshot channel, but it contains additional larger features.

And as a reminder, both the Adobe and Lucee servers contain important security updates, so make sure you're using them if your CommandBox servers are accessible to the public at all!  If you always start your servers with a semver range like so, you'll automatically get the new version the next time you start, but keep in mind you'll need to migrate any settings that were part of the old server version since we deploy a new server for you.

start cfengine=adobe@11
start cfengine=lucee@5.*

Since the Lucee snapshot and beta releases are not stable (they have a pre-release identifier in the version), you won't get those unless you specifically ask for them like this:

start cfengine=lucee@5.0.1-snapshot
start cfengine=lucee@5.1.0-beta

Otherwise, if you don't put a pre-release identifier in like "-snapshot" or "-beta" you'll always get a stable version only.

Add Your Comment

Recent Entries

One Language, Every Runtime: BoxLang Expands Beyond the Server

One Language, Every Runtime: BoxLang Expands Beyond the Server

Discover how BoxLang’s multi-runtime architecture helps developers build beyond the server with support for serverless functions, desktop applications, CI/CD workflows, Java integrations, containers, runtime management, and more.

Maria Jose Herrera
Maria Jose Herrera
June 04, 2026
MatchBox and WebAssembly: Running BoxLang in the Browser and at the Edge

MatchBox and WebAssembly: Running BoxLang in the Browser and at the Edge

The MatchBox open beta is live at https://boxlang.ortusbooks.com/boxlang-framework/matchbox, and it brings something genuinely new to the BoxLang ecosystem: a path into WebAssembly.

That means BoxLang code can now move into browser applications, static-site deployments, edge runtimes, and WASI-style containers - without requiring a JVM. The feature is still beta, but the core direction is already useful: write BoxLang, compile it with MatchBox, and ship the generated WASM artifact to wherever a small portable runtime makes sense.

Jacob Beers
Jacob Beers
June 04, 2026
BoxLang 1.14.0 : BoxSet is Here: BoxLang's New First-Class Set Type

BoxLang 1.14.0 : BoxSet is Here: BoxLang's New First-Class Set Type

BoxLang 1.14.0 ships something that JVM developers have wanted for a long time: a true first-class Set type baked directly into the language. Not a wrapper you reach for manually, not a createObject( "java", "java.util.HashSet" ) incantation you paste from a Stack Overflow answer years ago. A real BoxSet with literal syntax, operator overloads, a full functional pipeline, change listeners, JSON serialization, and deep Java interop.

Luis Majano
Luis Majano
June 03, 2026