![]() This release fixes a payload issue with the IQ Webhook for Application Evaluation that is triggered at Violation Alerts event. This release includes major performance enhancements to Advanced Legal Pack (ALP) Attribution Reports to avoid gateway timeouts when retrieving data for reports containing a large no. Gateway timeouts for ALP Attribution Reports This release resolves a duplicate primary key error condition that occurred in the Sonatype IQ Server database due to incompatibility in handling case sensitivity across platforms, specifically GitHub. This fixes the issue of malformed pull request (PR) layouts on encountering wildcard characters. This improvement ensures that Sonatype (Nexus) IQ for SCM is compatible with all wildcard characters used in markdown across supported developer platforms. Extended the Inclusion of Wildcard Characters in IQ for SCM The SBOM generation for all supported ecosystems has been improved to avoid such duplicates that resulted in invalid SBOM files. Scanning binaries that contain components with the same coordinates, but different hashes could lead to duplicates in the SBOM. ![]() Dependencies under the “full_requires” section have higher precedence over those under the “requires” section and will be excluded to avoid duplication. Release 163 (June 2023) Improvements Improved Identification of Conan DependenciesĪnalysis of conaninfo.txt file now does not show duplicate dependencies that were earlier being referenced in the “requires” and “full_requires” sections. If you are upgrading from an earlier version of IQ Server, please see Upgrading the IQ Server ![]() ![]() ![]() Download the latest version from here IQ Download and Compatibility. Check out our release notes for detailed descriptions of enhancements for each release.Īs a best practice, we recommend that you keep your IQ Server installation up to date, so you can benefit from the latest features and advancements in component intelligence. We're continuously improving Sonatype IQ Server products and features based on customer feedback. ![]()
0 Comments
Leave a Reply. |