You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jackrabbit.apache.org by re...@apache.org on 2025/03/20 10:28:29 UTC

(jackrabbit-site) branch main updated: update dependency-check instruction

This is an automated email from the ASF dual-hosted git repository.

reschke pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/jackrabbit-site.git


The following commit(s) were added to refs/heads/main by this push:
     new 334662b6 update dependency-check instruction
334662b6 is described below

commit 334662b6d3fdf1891473d2a5a5b942a4c7f1c234
Author: Julian Reschke <re...@apache.org>
AuthorDate: Thu Mar 20 11:28:21 2025 +0100

    update dependency-check instruction
---
 src/site/markdown/creating-releases.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/site/markdown/creating-releases.md b/src/site/markdown/creating-releases.md
index 2c8d5cf0..8e32e283 100644
--- a/src/site/markdown/creating-releases.md
+++ b/src/site/markdown/creating-releases.md
@@ -60,7 +60,7 @@ Release management tasks
 
 1. Check the CI status of the project ([Jackrabbit Jenkins](https://ci-builds.apache.org/job/Jackrabbit/))
 2. Consider checking the CVE database for vulnerabilities in dependencies,
-   using `mvn org.owasp:dependency-check-maven:9.0.9:aggregate` (first run will be slow because CVE
+   using `mvn org.owasp:dependency-check-maven:12.1.0:aggregate` (first run will be slow because CVE
    databases are downloaded and parsed). If dependencies need action, open tickets and make sure they
    are marked as candidate backports where applicable.        
 3. Make sure that an appropriate version for the release is entered in Jira