This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/io.camunda-zeebe-client-java-8.4.2
in repository https://gitbox.apache.org/repos/asf/camel.git
discard 0fa600277c6 Bump io.camunda:zeebe-client-java from 8.4.1 to 8.4.2
add e04fdeacb41 Regen for commit 6821ad911fcd2520bef181b11c5001b1fdc71229
(#13098)
add 8a6fdfd7c8a Bump aws-java-sdk2-version from 2.24.0 to 2.24.1 (#13099)
add 1442490e4f9 Bump xyz.rogfam:littleproxy from 2.1.1 to 2.1.2 (#13100)
add febbdc72820 Revert "Regen for commit
6821ad911fcd2520bef181b11c5001b1fdc71229 (#13098)" (#13105)
add 2f9a83d515f Bump io.camunda:zeebe-client-java from 8.4.1 to 8.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 (0fa600277c6)
\
N -- N -- N
refs/heads/dependabot/maven/io.camunda-zeebe-client-java-8.4.2 (2f9a83d515f)
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(-)
