Releases: albuch/sbt-dependency-check
Releases · albuch/sbt-dependency-check
v0.2.4
- Updated dependency-check-core to v3.1.2, see Dependency Check Release Notes for details
v0.2.3
v0.2.2
- Updated dependency-check-core to version 3.1.0, see Dependency Check release notes for details.
v0.2.1
v0.2.0
v0.1.10
- Cross build sbt-dependency-check for sbt 0.13.16 and 1.0.0-RC3 #23
- Updated Dependency Check core to v2.1.0 #21 Noteworthy changes:
- New setting
dependencyCheckScanSets
to add directories/files to the scan. Defaults tosrc/main/resources
- Ruby Bundle Audit Analyzer was promoted to not being experimental anymore
- New setting
- Reintroduced setting
dependencyCheckSuppressionFile
which was removed in last release. Setting is merged withdependencyCheckSuppressionFiles
when both are set. - Added missing setting for
dependencyCheckNSPAnalyzerUrl
to configure a custom URL to the Node Security Platform from DC core update to v2.0.0 - Updated the
dependencyCheckListSettings
task to print new settings since update to DC core v2.0.0 #24
v0.1.9
- Updated Dependency Check Core to v2.0.1 #16 , see Dependency Check v2.0.0 release notes for details. Noteworthy changes:
- New Analyzer for the Node Security Platform
- New report formats: CSV and JSON
- Support for multiple suppression files
- Bumped several dependencies and plugin versions #18 #17
Important: Breaking changes
dependencyCheckSuppressionFile
setting was changed fromOption[File]
toSeq[File]
and renamed todependencyCheckSuppressionFiles
to support multiple filesdependencyCheckFormat
has had it's default value changed from ALL to HTML.
v0.1.8
v0.1.7
- Added new configuration options - #12
- dependencyCheckHintsFile - The file path to the XML hints file - used to resolve false negatives.
- dependencyCheckCocoapodsEnabled - Sets whether or not the experimental Cocoapods Analyzer should be used.
- dependencyCheckSwiftEnabled - Sets whether or not the experimental Swift Package Manager Analyzer should be used.
- dependencyCheckBundleAuditEnabled - Sets whether or not the experimental Ruby Bundle Audit Analyzer should be used.
- dependencyCheckPathToBundleAudit - The path to bundle audit.