Skip to content

Commit 22b05cf

Browse files
Updating changelog
1 parent 87f2918 commit 22b05cf

File tree

1 file changed

+37
-0
lines changed

1 file changed

+37
-0
lines changed

docs/_posts/2018-09-06-v3.2.0.md

+37
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
---
2+
title: v3.2.0
3+
type: major
4+
---
5+
6+
**Features:**
7+
8+
* Configurable notifications of new vulnerabilities, vulnerable dependencies, analysis decision changes, and system events
9+
* Added Slack, Microsoft Teams, Outbound Webhook, Email, and system console notification publishers
10+
* Replaced NSP Check API with NPM Audit API
11+
* Added support for Sonatype OSS Index
12+
* Updated SPDX license IDs to v3.2
13+
* General improvements in logging when error conditions are encountered
14+
* Improvements to Dependency-Check XML report parsing
15+
* Added native CPE 2.2 and 2.3 parsing capability
16+
* Enhanced administrative interface with options for repositories and general configuration
17+
* Updated Java version used in Docker container
18+
19+
20+
**Fixes:**
21+
22+
* The audit table did not reflect the correct analysis and suppressed data
23+
* Added validation when processing Dependency-Check XML reports containing invalid Maven GAVs
24+
* Corrected issue with NVD mirroring affecting Docker containers and case-sensitive filesystems
25+
26+
**Upgrade Notes:**
27+
28+
* The PROJECT_CREATION_UPLOAD permission was introduced in this release. Existing API keys that need the
29+
ability to dynamically create projects (without providing them full PORTFOLIO_MANAGEMENT permission)
30+
will need this permission added to their account or through their team membership.
31+
32+
* The SYSTEM_CONFIGURATION permission was introduced in this release. Existing administrative users that
33+
need the ability to perform more general purpose system configurations need to add this permission to their
34+
accounts.
35+
36+
* Upgrades to v3.2.0 can be successfully performed from systems running v3.1.x. If a previous
37+
version is being used, an upgrade to 3.1.x is required prior to upgrading to v3.2.0.

0 commit comments

Comments
 (0)