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 f090c84 Regen for commit d0d073e77d875b62c81b6d701c935d971b392614
add e06258e Camel Google Secret Manager: Externalize auth library version
add 547ae15 Camel Google Secret Manager: Externalize auth library version
add df46e0d Sync deps
add f318f7b Regen for commit df46e0d88198d0cd6936a540d099fc3ce7a3fd92
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 (f090c84)
\
N -- N -- N refs/heads/regen_bot (f318f7b)
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 | 1 +
components/camel-google/camel-google-secret-manager/pom.xml | 2 +-
parent/pom.xml | 1 +
3 files changed, 3 insertions(+), 1 deletion(-)
