Read the blog post here: https://www.ortussolutions.com/blog/commandbox-520-released
-----------------------------------------------------------------
Today we are pleased to announce the final release of CommandBox 5.2.0. This release has been 5 months in the making and covers nearly 50 tickets. We've already covered the full list of new features and enhancements in our release candidate announcement which you can read here:
https://www.ortussolutions.com/blog/commandbox-520-release-candidate-ready-for-testing
After a month of RC testing, we've made several additional improvements and are ready to release.
Docs and DownloadsEverything has been documented already in the CommandBox docs here:
https://commandbox.ortusbooks.com/
And the final build is available on HomeBrew (for Mac users), our apt/yum repos (for Linux users), and our download page:
https://www.ortussolutions.com/products/commandbox#download
Major FeaturesWe've added a ton of new goodies to this release. The high level over is:
Read more about the new features and now to use them in our release candidate announcement.
Security FixesIt is highly recommended that you update to this new version of CommandBox right away for a number of security improvements.
I'm not going to give any specifics, but I wouldn't sit on this update. Read more about the new security additions in our release candidate announcement.
Community ContributorsWe'd like to recognize all the people in the community who sent pull requests that are a part of this release: Pete Freitag, Kai Koenig, Matthew Clemente, Bobby Hartsfield, Scott Steinbeck, Daniel Mejia, and Miguel Mathus!
Read more about the new features of 5.2.0 in this post.
Breaking ChangesWe work hard to make every CommandBox upgrade backwards compatible. There's a couple things that you may notice different in this release. They're both done to put security first and can be modified to get your original behavior back.
Since the CF Administrator is now blocked for traffic not coming from localhost when in production mode, you may need to explicitly open up the CF admin to make it accessible again if you needed it open to the public on a production server. Even with the profile set to production, you can activate just the CF admin like so:
server set web.blockCFAdmin=falseThe web server built into CommandBox will now only serve static files if their extension is found in a whitelist of acceptable files. This is to prevent prying eyes from hitting files they shouldn't be able to access on your server.
If you have a common static file you need to serve, you can add your own custom extensions to the list like so:
server set web.allowedExt=jar,exe,dllRead more about the breaking changes in our release candidate announcement.