This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/npm_and_yarn/docs/eslint-plugin-import-2.29.1
in repository https://gitbox.apache.org/repos/asf/camel.git
omit 95c42134302 chore(deps-dev): Bump eslint-plugin-import in /docs
add de92338ffe8 CAMEL-20853: Rest DSL: inlined routes should also work
when using onException.
add 524fbcc27e9 chore(deps): Bump huaweicloud-sdk-version from 3.1.99 to
3.1.100
add 185a5f061da chore(deps): Bump micrometer-tracing-version from 1.3.0 to
1.3.1
add bc184bb5aa4 chore(deps-dev): Bump gulp-cli from 2.3.0 to 3.0.0 in /docs
add eeee227c033 chore(deps-dev): Bump eslint-plugin-import in /docs
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 (95c42134302)
\
N -- N -- N
refs/heads/dependabot/npm_and_yarn/docs/eslint-plugin-import-2.29.1
(eeee227c033)
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:
.../java/org/apache/camel/impl/DefaultModel.java | 15 +-
docs/.pnp.cjs | 228 +++++++++++++++++-
docs/package.json | 2 +-
docs/yarn.lock | 257 ++++++++++++++++++++-
parent/pom.xml | 4 +-
5 files changed, 488 insertions(+), 18 deletions(-)
