This is an automated email from the ASF dual-hosted git repository.
slachiewicz pushed a change to branch
dependabot/maven/org.junit.jupiter-junit-jupiter-api-5.11.0
in repository https://gitbox.apache.org/repos/asf/maven-toolchains-plugin.git
omit 913117e Bump org.junit.jupiter:junit-jupiter-api from 5.10.3 to 5.11.0
add 9d761c0 [MTOOLCHAINS-55] Bump org.apache.maven.plugins:maven-plugins
from 42 to 43 (#39)
add 7552b5c [MTOOLCHAINS-55] Bump org.codehaus.plexus:plexus-xml from
3.0.0 to 3.0.1 (#34)
add db062ef [MTOOLCHAINS-55] Bump mavenVersion from 3.9.6 to 3.9.9 (#41)
add 39fe79a [MTOOLCHAINS-55] Bump
org.eclipse.sisu:org.eclipse.sisu.plexus from 0.9.0.M2 to 0.9.0.M3 (#36)
new 34b416b Bump org.junit.jupiter:junit-jupiter-api from 5.10.3 to 5.11.0
new affc16d [MTOOLCHAINS-55] Upgrade junit to 5.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 (913117e)
\
N -- N -- N
refs/heads/dependabot/maven/org.junit.jupiter-junit-jupiter-api-5.11.0 (affc16d)
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.
The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
pom.xml | 21 ++++++++++++++++-----
1 file changed, 16 insertions(+), 5 deletions(-)
