This is an automated email from the ASF dual-hosted git repository.
dependabot[bot] pushed a change to branch
dependabot/maven/org.codehaus.plexus-plexus-classworlds-2.10.0
in repository https://gitbox.apache.org/repos/asf/maven-assembly-plugin.git
discard 2ba877a1 Bump org.codehaus.plexus:plexus-classworlds from 2.9.0 to
2.10.0
add 5664d528 Bump org.codehaus.plexus:plexus-utils (#1300)
add 88abf6d3 Bump jaxen:jaxen from 2.0.0 to 2.0.1 (#1304)
add 88591328 Bump mavenVersion from 3.9.14 to 3.9.15 (#1303)
add 913c98cb Bump commons-io:commons-io from 2.21.0 to 2.22.0 (#1305)
add 3b134fbc Bump com.github.luben:zstd-jni from 1.5.7-7 to 1.5.7-8
add f0bf4514 Bump org.postgresql:postgresql in
/src/it/projects/bugs/massembly-730
add caeb88c0 Bump jaxen:jaxen from 2.0.1 to 2.0.2
add a506506d Bump org.apache.maven.plugins:maven-plugins from 47 to 48
(#1309)
add a970a967 Bump org.codehaus.plexus:plexus-classworlds from 2.9.0 to
2.11.0
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (2ba877a1)
\
N -- N -- N
refs/heads/dependabot/maven/org.codehaus.plexus-plexus-classworlds-2.10.0
(a970a967)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
pom.xml | 12 ++++++------
src/it/projects/basic-features/add-classpath/pom.xml | 2 +-
src/it/projects/bugs/massembly-730/pom.xml | 2 +-
3 files changed, 8 insertions(+), 8 deletions(-)
