This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch regen_bot_sbom
in repository https://gitbox.apache.org/repos/asf/camel-kamelets.git
omit d51110c7 Regen SBOM from commit
1bb4db9f98e3d5198be4b6ee405b99c77cab0e19
add 26f61966 Regen SBOM from commit
1bb4db9f98e3d5198be4b6ee405b99c77cab0e19 (#2312)
add 0dd64406 Updated CHANGELOG.md
add ad975561 Bump org.apache.maven.plugins:maven-javadoc-plugin from
3.11.1 to 3.11.2 (#2313)
add 7b26c579 Updated CHANGELOG.md
add 41c2d0a7 Bump actions/setup-go from 5.1.0 to 5.2.0 (#2315)
add 9b4c2c3a Updated CHANGELOG.md
add 6161a1f2 Updated CHANGELOG.md
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 (d51110c7)
\
N -- N -- N refs/heads/regen_bot_sbom (6161a1f2)
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/main-push-regen.yaml | 2 +-
.github/workflows/validate.yaml | 2 +-
CHANGELOG.md | 20 +++++++++++++++++++-
pom.xml | 2 +-
4 files changed, 22 insertions(+), 4 deletions(-)
