This is an automated email from the ASF dual-hosted git repository. github-bot pushed a change to branch dependabot/maven/micrometer-tracing-version-1.4.2 in repository https://gitbox.apache.org/repos/asf/camel.git
discard c4b04f915d1 chore(deps): Bump micrometer-tracing-version from 1.4.1 to 1.4.2 add d51726223db chore(deps): Bump gg.jte:jte from 3.1.15 to 3.1.16 add 5c16a7f1875 chore(deps): Bump org.redisson:redisson from 3.42.0 to 3.43.0 add 432046ac4dd chore(deps): Bump micrometer-tracing-version from 1.4.1 to 1.4.2 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 (c4b04f915d1) \ N -- N -- N refs/heads/dependabot/maven/micrometer-tracing-version-1.4.2 (432046ac4dd) 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 | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)