This is an automated email from the ASF dual-hosted git repository.
dependabot[bot] pushed a change to branch dependabot/maven/micrometer-3d244e347c
in repository https://gitbox.apache.org/repos/asf/camel.git
discard 6b9f76cb7c28 chore(deps): Bump the micrometer group across 1 directory
with 9 updates
add 215589a8abd4 chore(deps): Bump org.codehaus.plexus:plexus-archiver
add 9f2894aa9d1d chore(deps): Bump the micrometer group across 1 directory
with 9 updates
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 (6b9f76cb7c28)
\
N -- N -- N refs/heads/dependabot/maven/micrometer-3d244e347c
(9f2894aa9d1d)
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 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
