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.git
omit a856cc09651 Regen for commit c9fee17ec5a16128d7e72780adb3cbc8cd764ce1
add 55f8e2e69b6 Fixed javadoc in GCP Vault Configuration
add 70058e8f341 CAMEL-18535: Upgrade HBase to 2.5.0 (#8404)
add c6cd3d0163e Regen for commit 70058e8f34157fbd5930f218d1eb1a709d53e024
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 (a856cc09651)
\
N -- N -- N refs/heads/regen_bot (c6cd3d0163e)
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:
camel-dependencies/pom.xml | 2 +-
components/camel-hbase/pom.xml | 4 ++++
.../src/main/java/org/apache/camel/vault/GcpVaultConfiguration.java | 2 +-
parent/pom.xml | 2 +-
test-infra/camel-test-infra-hbase/pom.xml | 4 ++++
5 files changed, 11 insertions(+), 3 deletions(-)
