This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/maven/lucene-version-10.1.0
in repository https://gitbox.apache.org/repos/asf/camel.git
discard dcd830cb06a chore(deps): Bump lucene-version from 9.12.0 to 10.1.0
add 7b2757e6616 chore(deps): Bump org.mnode.ical4j:ical4j from 4.0.7 to
4.0.8 (#16631)
add c35d976489a chore(deps): Bump aws-java-sdk2-version from 2.29.38 to
2.29.39 (#16632)
add df333566c0b chore(deps): Bump org.freemarker:freemarker from 2.3.33 to
2.3.34 (#16637)
add 23ec6b59fe2 chore(deps): Bump logback-version from 1.5.14 to 1.5.15
(#16633)
add 06d92be1ba2 chore(deps): Bump hapi-fhir-version from 7.6.0 to 7.6.1
(#16634)
add 0eb0d4e674f chore(deps): Bump org.redisson:redisson from 3.40.2 to
3.41.0 (#16639)
add cf5452b7f57 chore(deps): Bump lucene-version from 9.12.0 to 10.1.0
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 (dcd830cb06a)
\
N -- N -- N refs/heads/dependabot/maven/lucene-version-10.1.0
(cf5452b7f57)
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:
parent/pom.xml | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
