Release 3.3 notes ------------------- yCrash Server - Features and Fixes: ---------------------------------- + Optimized the repeating statements detection logic to improve processing performance and reduce analysis time. + Introduced a Scorer mechanism in Error Analysis to minimize false-positive error detections. + Added a new feature: RCA Executive Summary. An AI-generated summary is now displayed under the “AI Overview” section on the yCrash RCA page. When an artifact bundle is uploaded, AI Overview automatically generates a concise incident summary by analyzing captured artifacts such as GC logs, thread dumps, heap substitutes, system metrics, network analysis reports, device errors, and application logs. Users can also select “Dive Deeper in AI Mode” to launch yCrash Buddy and ask follow-up questions related to the incident. + Added the Swagger API Documentation page for easier API exploration and integration. Additional details are available here: https://docs.ycrash.io/ycrash-features/ycrash-api-reference-swagger-ui.html + Fixed issues related to .NET log analysis. + Introduced AppLog Comparison, enabling comparison of multiple application logs within the Compare Report section. + Added GCeasy AI support. GCeasy now includes a Deterministic AI tab that delivers AI-powered GC log analysis and provides answers to GC-related questions through an interactive chat interface, helping users identify and resolve GC issues more efficiently. yc-360-Script - Features and Fixes: ---------------------------------- + Added support for .NET applications in M3 mode. + Introduced automatic AppRuntime detection, removing the requirement for manual appRuntime configuration. + Enhanced error messages across the application to improve troubleshooting and user experience. + Added a .NET helper utility to capture logs from 32-bit Windows systems. + Upgraded the Go toolchain to v1.26.3 to address reported standard library vulnerabilities. + Updated vulnerable Go dependencies and rebuilt binaries using the latest patched Go runtime. + Resolved compatibility issues in the golangci/golangci-lint-action CI workflow caused by the Go version upgrade