Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump dependency-check-maven from 5.2.1 to 6.0.3 #34

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dependabot-preview[bot]
Copy link
Contributor

Bumps dependency-check-maven from 5.2.1 to 6.0.3.

Release notes

Sourced from dependency-check-maven's releases.

v6.0.3

  • Added a bash command completion script (see #2916); to add completion to your shell completion-for-dependency-check.sh can be found in the bin directory of the CLI:
    $ source completion-for-dependency-check.sh
  • An experimental PIP File Analyzer was added (see #2877).
  • Analysis of Node JS produced several false positives (see #2796); the analysis has been updated to reduce the number of false positives.
    • If analyzing Node JS projects it is highly recommended to disable the Node JS Analyzer and solely rely on the Node Audit Analyzer. There are plans to rework Node JS analysis in a future release.
  • Support for external Oracle databases has been add for the 6.x releases (see #2899)
  • Resolved several reported false positives.
  • Several other bug fixes have been implemented; see the full listing of changes.

v6.0.2

  • The project is migrating from hosting the release archives on Bintray and moving them to Github under the assets for each release
    • Please update any automation you have to point to the new location.
  • Npm Audit Analyzer now correctly skips dev dependencies (--nodeAuditSkipDevDependencies); see #2482.
  • GoLang Analyzer now scans transitive dependencies; see #2680.
  • Several bug fixes found in 6.0.1.

6.0.1

  • Improved error messages when upgrading from 5.x to 6.x; due to breaking database changes if the old database schema is detected an error message is produced indicating that the old database should be purged.

  • Fixed the database path for the Ant and Gradle plugins.

  • Added locking around the RetireJS updates to resolve read/write conflicts in CI environments.

  • Full listing of changes.

v6.0.0

  • Updated database schema; this is a breaking change and anyone using an external database or those whom specify the data directory will need recreate the database (including users of the docker image). The schema changes were made to:

    • Improve the CVSS data, when available, per #2547
    • Improve the way that ecosystems are determined
    • Improve the update performance of external databases
  • Users with an external Oracle database will not be able to upgrade as jeremylong/DependencyCheck#2755 has not been resolved - as such, version 6.0.0 does not support Oracle.

  • Users mirroring the NVD - ODC 6.0.0 requires the use of the version 1.1 data feeds - please ensure you are using 1.1 not the 1.0 data feed.

  • Full listing of changes.

v5.3.2

Version 5.3.2 was published on March 26, 2020; see the release notes.

Changelog

Sourced from dependency-check-maven's changelog.

Version 6.0.3 (2020-11-03)

Changes

  • Added a bash command completion script (see #2916); to add completion to your shell completion-for-dependency-check.sh can be found in the bin directory of the CLI:
    $ source completion-for-dependency-check.sh
  • An experimental PIP File Analyzer was added (see #2877).
  • Analysis of Node JS produced several false positives (see #2796); the analysis has been updated to reduce the number of false positives.
    • If analyzing Node JS projects it is highly recommended to disable the Node JS Analyzer and solely rely on the Node Audit Analyzer. There are plans to rework Node JS analysis in a future release.
  • Support for external Oracle databases has been add for the 6.x releases (see #2899)
  • Resolved several reported false positives.
  • Several other bug fixes have been implemented; see the full listing of changes.

Version 6.0.2 (2020-09-27)

Changes

  • The project is migrating from hosting the release archives on Bintray and moving them to Github under the assets for each release

    • Please update any automation you have to point to the new location.
  • Npm Audit Analyzer now correctly skips dev dependencies (--nodeAuditSkipDevDependencies); see #2482.

  • GoLang Analyzer now scans transitive dependencies; see #2680.

  • Several bug fixes found in 6.0.1.

  • Full listing of changes.

Version 6.0.1 (2020-09-13)

Changes

  • Improved error messages when upgrading from 5.x to 6.x; due to breaking database changes if the old database schema is detected an error message is produced indicating that the old database should be purged.

  • Fixed the database path for the Ant and Gradle plugins.

  • Added locking around the RetireJS updates to resolve read/write conflicts in CI environments.

  • Full listing of changes.

Version 6.0.0 (2020-09-07)

Changes

  • Updated database schema; this is a breaking change and anyone using an external database or those whom specify the data directory will need recreate the database (including users of the docker image). The schema changes were made to:
Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Pull request limits (per update run and/or open at any time)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

@dependabot-preview dependabot-preview bot added the dependencies Pull requests that update a dependency file label Nov 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants