This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/org.apache.maven.plugins-maven-assembly-plugin-3.6.0
in repository https://gitbox.apache.org/repos/asf/camel-k-runtime.git
discard 2d82ad87 build(deps): bump
org.apache.maven.plugins:maven-assembly-plugin
add 93e0e75d chore: update changelog
add 4e068d42 chore: update SBOM
add 54e66a28 build(deps): bump
org.apache.maven.plugins:maven-dependency-plugin
add d1db680f build(deps): bump
org.apache.maven.plugins:maven-javadoc-plugin
add f3ed5938 build(deps): bump
org.apache.maven.plugins:maven-assembly-plugin
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 (2d82ad87)
\
N -- N -- N
refs/heads/dependabot/maven/org.apache.maven.plugins-maven-assembly-plugin-3.6.0
(f3ed5938)
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:
CHANGELOG.md | 30 +-
camel-k-runtime-sbom/camel-k-runtime-sbom.json | 10786 +++++++++++------------
camel-k-runtime-sbom/camel-k-runtime-sbom.xml | 10558 +++++++++++-----------
pom.xml | 4 +-
support/camel-k-runtime-bom/pom.xml | 2 +-
5 files changed, 10464 insertions(+), 10916 deletions(-)
