Blog

ColdBox 2.6.2 Fixes and Patches

Luis Majano January 08, 2009

Spread the word

Luis Majano

January 08, 2009

Spread the word


Share your thoughts

There have been some bug fixes and patches to 2.6.2 that can be located on our daily build and SVN.  If you are curious of what these bugs are and how milestone 2.6.3 is shaping up, please go here and check it out.

2.6.3 will be our last maintenance release in our 2.X ColdBox Series before we start development on ColdBox 3.0.0 which will be a nice move ahead from our past 15 versions.  We have tons of exciting updates, surprises and performance updates for our 3.0.0 version.  You can also check out how this release is shaping up by visiting the milestone here.

Add Your Comment

Recent Entries

Your Development Team Is at Capacity. Here’s How to Keep Critical Work Moving!

Your Development Team Is at Capacity. Here’s How to Keep Critical Work Moving!

The problem is not that your team lacks priorities.It is that maintenance, delivery, and long-term improvement are competing for the same people.

For companies running business-critical CFML, ColdFusion, or BoxLang applications, that pressure can be especially difficult to solve. Experienced developers are not always easy to hire quickly, application knowledge may be concentrated in one or two people, and a generalist may need significant context before taking ownership of the work. A permanent hire can also require a significant investment in recruiting, compensation, onboarding, and long-term capacity even when the immediate need is a specific project, urgent maintenance, or a period of transition.

Maria Jose Herrera
Maria Jose Herrera
September 18, 2026
Copy of BoxLang AI 3.4 Blog Series Part 5 : Reasoning Without the Guesswork

Copy of BoxLang AI 3.4 Blog Series Part 5 : Reasoning Without the Guesswork

Reasoning-capable models have been usable in BoxLang AI for a while. params passes straight through to the provider body, so params: { thinking: { type: "enabled", budget_tokens: 10000 } } for Claude, or params: { reasoning_effort: "high" } for OpenAI, already reached the API. What never worked was reading the reasoning back. It was parsed out on arrival and silently dropped. In 3.4.0, that's fixed, and it's fixed the same way for every provider.

Luis Majano
Luis Majano
September 15, 2026