This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch regen_bot
in repository https://gitbox.apache.org/repos/asf/camel-kamelets.git
omit 280dc4d1e Regen for commit 6935685a7a2eaa770146599701b51c0b15ed258c
add 925384f22 Bump org.postgresql:postgresql from 42.7.7 to 42.7.8 (#2583)
add 74b4adb88 Regen for commit 6935685a7a2eaa770146599701b51c0b15ed258c
(#2584)
add 73494ee3f Regen for commit 74b4adb88f2aa274669cb0e104b37b79583d50bd
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 (280dc4d1e)
\
N -- N -- N refs/heads/regen_bot (73494ee3f)
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:
kamelets/postgresql-sink.kamelet.yaml | 2 +-
kamelets/postgresql-source.kamelet.yaml | 2 +-
.../src/main/resources/kamelets/postgresql-sink.kamelet.yaml | 2 +-
.../src/main/resources/kamelets/postgresql-source.kamelet.yaml | 2 +-
pom.xml | 2 +-
5 files changed, 5 insertions(+), 5 deletions(-)
