This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/maven-plugin-tools-3.x/org.jsoup-jsoup-1.22.1
in repository https://gitbox.apache.org/repos/asf/maven-plugin-tools.git
discard 3173dcc0 Bump org.jsoup:jsoup from 1.19.1 to 1.22.1
add a1ec6b58 Bump org.codehaus.plexus:plexus-archiver from 4.10.4 to
4.11.0 (#1062)
add a012db47 Bump net.bytebuddy:byte-buddy from 1.18.3 to 1.18.4
add 1b4f661c Bump
org.apache.maven.plugin-testing:maven-plugin-testing-harness
add be7874bf Bump org.assertj:assertj-core from 3.27.6 to 3.27.7
add 61710db3 Bump org.junit:junit-bom from 5.14.0 to 5.14.2
add fd93edb5 Bump
org.apache.maven.plugin-testing:maven-plugin-testing-harness (#1073)
add 35de0402 Bump org.jsoup:jsoup from 1.19.1 to 1.22.1
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 (3173dcc0)
\
N -- N -- N
refs/heads/dependabot/maven/maven-plugin-tools-3.x/org.jsoup-jsoup-1.22.1
(35de0402)
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:
maven-plugin-tools-annotations/pom.xml | 2 +-
pom.xml | 8 ++++----
2 files changed, 5 insertions(+), 5 deletions(-)
