This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/org.codehaus.mojo-versions-maven-plugin-2.21.0
in repository https://gitbox.apache.org/repos/asf/camel.git
discard 9cebcb435519 chore(deps-dev): Bump
org.codehaus.mojo:versions-maven-plugin
add e3562403f6b9 chore(deps): Bump
com.google.cloud:google-cloud-pubsublite (#20928)
add fa7e23b6cb41 chore(deps): Bump com.cedarsoftware:java-util from 4.83.0
to 4.84.0 (#20930)
add d9a5493a7d44 chore(deps): Bump gg.jte:jte from 3.2.1 to 3.2.2 (#20931)
add e78ea010b3c6 chore(deps): Bump com.google.cloud:google-cloud-bigquery
(#20934)
add 0448fa60be21 chore(deps-dev): Bump
org.codehaus.mojo:versions-maven-plugin
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 (9cebcb435519)
\
N -- N -- N
refs/heads/dependabot/maven/org.codehaus.mojo-versions-maven-plugin-2.21.0
(0448fa60be21)
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:
parent/pom.xml | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
