This is an automated email from the ASF dual-hosted git repository. github-bot pushed a change to branch dependabot/maven/com.cloudbees.thirdparty-zendesk-java-client-0.24.2 in repository https://gitbox.apache.org/repos/asf/camel.git
discard 27751cb1d78 Bump com.cloudbees.thirdparty:zendesk-java-client from 0.23.0 to 0.24.2 add 29530e17e3b Bump aws-java-sdk2-version from 2.23.11 to 2.23.12 (#12918) add 1949972c8a3 Bump com.googlecode.libphonenumber:libphonenumber (#12923) add 948d0ec8626 Bump io.camunda:zeebe-client-java from 8.4.0 to 8.4.1 (#12924) add b53d0e48bec Bump com.cloudbees.thirdparty:zendesk-java-client from 0.23.0 to 0.24.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 (27751cb1d78) \ N -- N -- N refs/heads/dependabot/maven/com.cloudbees.thirdparty-zendesk-java-client-0.24.2 (b53d0e48bec) 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(-)