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 8c6ac329895 Regen for commit d45d6bcaf4c4e5d4ccd150d4bfe125ab38b14466
add 15888902b55 Bump json5 from 1.0.1 to 1.0.2 in /docs
add 422faed77c5 (chores) camel-core: disabled flaky test on Github
add 6cfe2ecde01 Regen for commit 422faed77c55e323c595dcdff7379e920fbf80c7
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 (8c6ac329895)
\
N -- N -- N refs/heads/regen_bot (6cfe2ecde01)
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:
.../management/ManagedPooledExchangeTest.java | 2 ++
docs/.pnp.cjs | 8 ++++----
.../json5-npm-1.0.1-647fc8794b-e76ea23dbb.zip | Bin 29177 -> 0 bytes
.../json5-npm-1.0.2-9607f93e30-866458a8c5.zip | Bin 0 -> 25520 bytes
docs/.yarn/install-state.gz | Bin 568999 -> 569077 bytes
docs/yarn.lock | 6 +++---
6 files changed, 9 insertions(+), 7 deletions(-)
delete mode 100644 docs/.yarn/cache/json5-npm-1.0.1-647fc8794b-e76ea23dbb.zip
create mode 100644 docs/.yarn/cache/json5-npm-1.0.2-9607f93e30-866458a8c5.zip
