ColdBox 6.8.2 Released

CacheBox, ColdBox MVC, ColdFusion, LogBox, News, Releases, WireBox

Luis Majano May 02, 2023

Spread the word

Luis Majano

May 02, 2023

Spread the word

Share your thoughts

Today is a happy day, that we get to release ColdBox v6.8.2. This is our first in our commitment to an LTS release cycle for ColdBox with the upcoming ColdBox 7 release.

Updating ColdBox


update coldbox

# If you are using standalone libraries, then update those
update wirebox
update cachebox
update logbox

You can find our what's new document here: https://coldbox.ortusbooks.com/intro/release-history/whats-new-with-6.8.2.

LTS Support

For all ColdBox releases, updates are provided for 12 months and security fixes are provided for 2 years after the next major release.

ColdBox 6.x will receive bug fixes until 2024 and security fixes until 2025.

Version	Release	Updates	Security Fixes
6.x	2022	2023	2025
7.x	2023	2024	2026
8.x	2024	2025	2027
9.x	2025	2026	2028

Release Notes

Added

Github actions for LTS Releases
LTS Updates

Bugs

COLDBOX-1219 CFProvider ACF versions are Hard-Coded
WIREBOX-132 WireBox caches Singletons even if their autowired dependencies throw exceptions.

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.

BoxLang 1.14.0 : Introducing Inner Classes

BoxLang has always embraced a simple truth: the way you organize code shapes the way you think about problems. For a long time, if you needed a helper class, you needed a file. One class, one .bx file, no exceptions. That's clean and predictable, but it creates real friction when a class is tightly coupled to exactly one caller and has no business existing anywhere else.

Blog