This is an automated email from the ASF dual-hosted git repository.
github-actions[bot] pushed a change to branch regen_bot
in repository https://gitbox.apache.org/repos/asf/camel-kamelets.git
omit 4934e8751 Regen for commit 3783d8742a152d621948b480dbb3c247501ccffd
add 52d729df4 Regen for commit 3783d8742a152d621948b480dbb3c247501ccffd
(#3108)
add db253b3ae chore(deps): bump actions/setup-java from 6.0.1 to 6.1.0
(#3106)
add b3c773004 chore(deps): bump com.amazon.redshift:redshift-jdbc42 (#3107)
add 359a4812b Regen for commit b3c773004a59ba44c2d7741da5b4a5fa5ffdd7fa
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 (4934e8751)
\
N -- N -- N refs/heads/regen_bot (359a4812b)
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 +-
.github/workflows/validate.yaml | 2 +-
camel-kamelets-sbom/camel-kamelets-catalog-sbom.json | 12 ++++++------
kamelets/aws-redshift-sink.kamelet.yaml | 2 +-
kamelets/aws-redshift-source.kamelet.yaml | 2 +-
.../main/resources/kamelets/aws-redshift-sink.kamelet.yaml | 2 +-
.../main/resources/kamelets/aws-redshift-source.kamelet.yaml | 2 +-
pom.xml | 2 +-
12 files changed, 18 insertions(+), 18 deletions(-)
