This is an automated email from the ASF dual-hosted git repository.
cstamas pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-site.git
The following commit(s) were added to refs/heads/master by this push:
new f526c2ab Update release notes of 3.9.13 to use 3.19.14 (#1534)
f526c2ab is described below
commit f526c2abe707538f44a1116ee933c71a9d5d6797
Author: Matthias Bünger <[email protected]>
AuthorDate: Thu Mar 12 12:47:46 2026 +0100
Update release notes of 3.9.13 to use 3.19.14 (#1534)
Co-authored-by: Matthias Bünger <[email protected]>
---
content/markdown/docs/3.9.13/release-notes.md | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/content/markdown/docs/3.9.13/release-notes.md
b/content/markdown/docs/3.9.13/release-notes.md
index c993049a..fbac8d18 100644
--- a/content/markdown/docs/3.9.13/release-notes.md
+++ b/content/markdown/docs/3.9.13/release-notes.md
@@ -61,9 +61,8 @@ For a full list of changes, please refer to the [GitHub
release page](https://gi
After the release, we discovered that the distribution contains several
testing libraries, see [GH-11762](https://github.com/apache/maven/issues/11762).
While this is not an issue per se (maven-core does not export these
dependencies, they are "confined" in core classloader), in case you perform
dependency analysis (ie using Enforcer) **and** you depend on `maven-core` or
any artifact that has `maven-core` in its tree, you may hit issues.
-In this case, remaining on 3.9.12 release is the recommended workaround.
-We are working on 3.9.14 release with this issue fixed, and it will happen as
soon as possible.
+Please upgrade to 3.9.14, in which this issue is fixed.
## Potentially Breaking Core Changes (if migrating from 3.8.x)
