Releases: MindscapeHQ/raygun4cfml
2.0.1 - ACF/CGI bugfix
What's Changed
fix: Issue with ACF's CGI scope when using content filtering
Full Changelog: 2.0.0...2.0.1
2.0.0 - Modernisation Rewrite
What's Changed
Complete re-write, breaking API changes and changes in essential functionality:
- chore: Raygun4CFML is now entirely written in CFML script.
- feature: The original stack trace is now tracked in the stack trace field, not the CFML
TagContext
. The latter is now in the exception's data section, where available. - feature: There is now proper support for nested exceptions (based on existence of
cause
field). - feature: Content filtering (
RaygunContentFilter
), user identifier (RaygunIdentifierMessage
) and user custom data (RaygunUserCustomData
) are now using the builder-pattern approach to be setup forRaygunClient
. - fix: Size of raw data can be configured (#42).
- fix: SQL exception tracking has been improved (#44).
- chore: Constants are now tracked in their own static component and some can be overwritten by
RaygunSettings
. - chore:
ProductCheck
andRaygunInternalTools
are now static components. - feature: CFML engine is being tracked in Raygun's Environment tab now.
- feature: Samples in
/samples
have been reworked. - tests: Unit/Integration tests are in
/tests/specs
. - chore: Code formatting via
run-script format
was added for Commandbox. - tests: Project contains custom CFML server declarations for testing on ports (port 9191 upwards).
- documentation: All files have improved code documentation.
Engine-specific changes:
- chore: Support for Adobe ColdFusion before ACF 2021 has been stopped. ACF 2018 and earlier are - as CFML engines go - not supported any more, please upgrade your platforms.
- chore: Support for any versions of Railo has been stopped. Lucee support is set to Lucee 5.4 and newer, but this might be extended to 5.3 in a future 2.0.0 pre-release.
- chore: Support for Boxlang 1.0.0 has been added.
Full Changelog: 1.7.0...2.0.0
1.7.0 - Various fixes and improvments
fix: Fixes issues around non-existent HTTP request objects when run on ACF and in a thread context
fix: Fixes access to JVM memory beans depending on JVM settings and JVM type available
chore: Minimum requirements are now Lucee 5+ anmd ACF 2018+
fix: Fixes issue with content filter not trailing deep into payload
Full Changelog: 1.6.0...1.7.0
1.6.0 - Improved filtering for sensitive data
feature: Applying content/sensitivity filter later and against the full payload before being sent to Raygun.
fix: fixed error in exception message on recent versions of ACF.
1.5.0 - async sending and groupingKey support
feature: Added .sendAsync() entry point wrapping the HTTP call into its own thread.
feature: Supports groupingKey now
fix: Improving handling of getHTTPRequestData in RaygunRequestMessage
chore: Regorganisation of code in RaygunClient
chore: Changed HTTP endpoint to .com
1.4.0 - Better support for certain types of stack traces
What's Changed
- 1.4.0 changes by @TheRealAgentK in #43
- Supporting stack traces where certain elements (like TagContext) don't exist
- Support for specifc Java strack traces stemming from asynchronous handling
Full Changelog: 1.3.1...1.4.0
1.3.1 - Conditional physical memory tracking
- On Java 8, physical memory tracking is back with this release. On Java 9+, physical memory tracking will work, provided the respectively necesarry JVM modules are available and opened up.
1.3.0 - Memory usage tracking changes
- Changed memory usage tracking to be compatible with JDK 9+ and changed to tracking virtual (heap) memory instead of physical memory.
1.2.1 - Minor changes to stack trace and request URL
- Added location property to box.json to point to MindscapeHQ repo.
- Additional minor changes to stacktrace handling. Request URL now combines script name and path info from CGI.
1.2.0 - Improved support for Lucee and ACF 2021
- Better stack traces on new platforms
- Version support