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-n-17.16.2
in repository https://gitbox.apache.org/repos/asf/camel.git
discard aaa6de62c74 chore(deps-dev): Bump eslint-plugin-n from 17.15.1 to
17.16.2 in /docs
add 703b6df3509 chore(deps): Bump com.pubnub:pubnub-gson from 10.4.3 to
10.4.5 (#17397)
add 62c1382b248 chore(deps): Bump org.mnode.ical4j:ical4j from 4.1.0 to
4.1.1 (#17398)
add ca84d4834e0 chore(deps): Bump io.opentelemetry:opentelemetry-bom-alpha
(#17399)
add 0203aecbfa3 chore(deps): Bump
com.google.apis:google-api-services-drive (#17400)
add 4bb39dba1ff chore(deps): Bump com.cedarsoftware:java-util from 3.1.1
to 3.2.0 (#17401)
add da3f8bca6a3 chore(deps-dev): Bump eslint-plugin-n from 17.15.1 to
17.16.2 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 (aaa6de62c74)
\
N -- N -- N
refs/heads/dependabot/npm_and_yarn/docs/eslint-plugin-n-17.16.2 (da3f8bca6a3)
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:
components/camel-opentelemetry/pom.xml | 2 +-
parent/pom.xml | 8 ++++----
2 files changed, 5 insertions(+), 5 deletions(-)
