This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/mvnd-1.x/jakarta.inject-jakarta.inject-api-2.0.1.MR
in repository https://gitbox.apache.org/repos/asf/maven-mvnd.git
discard 2b54c94c Bump jakarta.inject:jakarta.inject-api from 1.0 to 2.0.1.MR
add 6cf4e92b Bump native-maven-plugin from 0.10.2 to 0.10.3 (#1144)
add fc462432 Bump org.apache.maven.plugins:maven-javadoc-plugin from
3.10.0 to 3.10.1
add 5a9eced1 Bump jline.version from 3.27.0 to 3.27.1 (#1167)
add c35ec2d7 Bump org.graalvm.nativeimage:svm from 24.1.0 to 24.1.1 (#1168)
add 2662c71b Bump jakarta.inject:jakarta.inject-api from 1.0 to 2.0.1.MR
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 (2b54c94c)
\
N -- N -- N
refs/heads/dependabot/maven/mvnd-1.x/jakarta.inject-jakarta.inject-api-2.0.1.MR
(2662c71b)
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:
client/pom.xml | 58 +++++++++++++++++++++++++++++++----------------
integration-tests/pom.xml | 4 ++--
pom.xml | 8 +++----
3 files changed, 45 insertions(+), 25 deletions(-)
