This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/maven/resolver.version-1.7.2
in repository https://gitbox.apache.org/repos/asf/maven-indexer.git.
omit f03619a Bump resolver.version from 1.6.2 to 1.7.2
add 85ad0d4 Bump logback-core from 1.2.3 to 1.2.6
add 037a50b Bump logback-classic from 1.2.3 to 1.2.6
add 2544627 Bump slf4j-simple from 1.7.30 to 1.7.32
add e4112d6 Bump version.spring from 5.3.9 to 5.3.10
add 2416193 Bump eclipse-sisu.version from 0.3.4 to 0.3.5
add c1d5fc5 Bump maven.version from 3.8.2 to 3.8.3
add ec1d567 Bump resolver.version from 1.6.2 to 1.7.2
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 (f03619a)
\
N -- N -- N refs/heads/dependabot/maven/resolver.version-1.7.2
(ec1d567)
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:
indexer-examples/indexer-examples-spring/pom.xml | 2 +-
pom.xml | 10 +++++-----
2 files changed, 6 insertions(+), 6 deletions(-)
