This is an automated email from the ASF dual-hosted git repository.
github-actions[bot] pushed a change to branch regen_bot_sbom
in repository https://gitbox.apache.org/repos/asf/camel-kamelets.git
omit c5916b3d9 Regen SBOM from commit
838ae31a739c9cc6db023628face685b82671c98
add c8e83a685 Regen SBOM from commit
838ae31a739c9cc6db023628face685b82671c98 (#2862)
add 4939ac41c chore(deps): bump actions/setup-java from 5.2.0 to 5.3.0
(#2863)
add 5088710ae Regen SBOM from commit
4939ac41ce68d093668c59d9b9f9b02dc3515e24
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 (c5916b3d9)
\
N -- N -- N refs/heads/regen_bot_sbom (5088710ae)
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:
.github/workflows/ci-build.yml | 4 +--
.github/workflows/generate-sbom-main.yml | 2 +-
.github/workflows/integration-tests.yaml | 2 +-
.github/workflows/java-tests.yaml | 2 +-
.github/workflows/main-push-regen.yaml | 2 +-
camel-kamelets-sbom/camel-kamelets-sbom.json | 48 ++++++++++++++--------------
camel-kamelets-sbom/camel-kamelets-sbom.xml | 48 ++++++++++++++--------------
7 files changed, 54 insertions(+), 54 deletions(-)
