This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/maven/logback-version-1.4.1
in repository https://gitbox.apache.org/repos/asf/camel-k-runtime.git
discard 0be2369f build(deps): bump logback-version from 1.2.11 to 1.4.1
add 4d785bdc build(deps): bump maven-pmd-plugin from 3.18.0 to 3.19.0
add ed849a52 build(deps): bump logback-version from 1.2.11 to 1.4.0
add 2c6bf5db Align to Camel Quarkus 2.13.0
add b0f14b25 Adding commons-io dependency to camel-k-core
add 3b658ac3 build(deps): bump logback-version from 1.2.11 to 1.4.1
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 (0be2369f)
\
N -- N -- N refs/heads/dependabot/maven/logback-version-1.4.1
(3b658ac3)
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:
camel-k-core/deployment/pom.xml | 4 ++++
pom.xml | 38 +++++++++++++++++++++++++++++++++-----
2 files changed, 37 insertions(+), 5 deletions(-)
