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 f8ef9f818a8 Regen for commit c00f547730127db61dbf8c2296a1f4d14ea37035
add 0af0ef0fa46 Regen for commit c00f547730127db61dbf8c2296a1f4d14ea37035
(#9298)
add 299d7feaae7 jakarta-enterprise-cdi-api-version property is listed
twice in parent/pom.xml (#9299)
add 78b8c943bde Upgrade Azurite to 3.21.0 (#9301)
add 4a7ee69e641 Regen for commit 78b8c943bde7400f27319f0805f741f1cdf32c71
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 (f8ef9f818a8)
\
N -- N -- N refs/heads/regen_bot (4a7ee69e641)
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 -
parent/pom.xml | 1 -
.../apache/camel/test/infra/azure/common/services/AzuriteContainer.java | 2 +-
3 files changed, 1 insertion(+), 3 deletions(-)
