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.
discard ec1d567 Bump resolver.version from 1.6.2 to 1.7.2
add faffe3c [MINDEXER-129] Shared GitHub Actions
add beaa697 Bump maven.version from 3.8.3 to 3.8.4
add b8851dd Bump logback-classic from 1.2.6 to 1.2.7
add e3ad742 Bump checkstyle from 8.41.1 to 9.1
add 253a7d8 Bump maven-shared-resources from 3 to 4
add 105c6b4 Bump version.spring from 5.3.10 to 5.3.13
add 836f3bf 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 (ec1d567)
\
N -- N -- N refs/heads/dependabot/maven/resolver.version-1.7.2
(836f3bf)
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:
.../workflows/maven-verify.yml | 22 +++++++++++++++-------
indexer-examples/indexer-examples-spring/pom.xml | 2 +-
pom.xml | 8 ++++----
3 files changed, 20 insertions(+), 12 deletions(-)
copy deploySite.sh => .github/workflows/maven-verify.yml (74%)
