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 6b26d2c Regen for commit 96bb4a48508a896a271cb46821c289ba5beacfb2
add 586fabb Upgrade Drools to version 7.45.0.Final
add f00df5e Upgrade Optaplanner to version 7.45.0.Final
add cf0e7e9 Upgrade Kie to version 7.45.0.Final
add aa327b2 Upgrade JBPM to version 7.45.0.Final
add 7d10a55 Regen catalog
add f89af35 Regen for commit 7d10a55cd14381c97a28a33522974ccf6c93b4ee
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 (6b26d2c)
\
N -- N -- N refs/heads/regen_bot (f89af35)
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 | 8 ++++----
parent/pom.xml | 8 ++++----
2 files changed, 8 insertions(+), 8 deletions(-)
