This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch regen_bot
in repository https://gitbox.apache.org/repos/asf/camel.git
omit 116a1ff3a63 Regen for commit fb6b25bdf7ecb8da1aa8ac36b0c19a3b7a4ca378
add bf8baeb0f21 chore(deps): Bump aws-java-sdk2-version from 2.28.16 to
2.28.17 (#15874)
add dcb8d79fae4 chore(deps): Bump org.jgroups:jgroups from 5.3.12.Final to
5.3.13.Final (#15876)
add 77b9e172519 chore(deps): Bump org.atmosphere:atmosphere-runtime
(#15875)
add f3ffe28c944 Regen for commit b7b4f0aad085a71165f1c5b014989d89542a654d
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 (116a1ff3a63)
\
N -- N -- N refs/heads/regen_bot (f3ffe28c944)
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 | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
