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 db95c195c3c Regen for commit c7663e170f47ab371ed7569cfb2dd934424277df
add 60c2dc01203 Regen for commit c7663e170f47ab371ed7569cfb2dd934424277df
(#12100)
add 1c22ce4c95f Regen for commit d196cb418eeb731f432620ca0c45645800f2dd02
(#12099)
add 44ed6739f08 Update known releases in catalog
add 60f6fc9f188 Regen for commit 44ed6739f089b239d72c85eb3e15ed354abc24e7
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 (db95c195c3c)
\
N -- N -- N refs/heads/regen_bot (60f6fc9f188)
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:
.../org/apache/camel/catalog/releases/camel-releases.json | 7 +++++++
1 file changed, 7 insertions(+)
