This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/maven.dependency.version-3.8.2
in repository https://gitbox.apache.org/repos/asf/commons-release-plugin.git.
discard 44ca37e Bump maven.dependency.version from 3.8.1 to 3.8.2
add e3d4b2c Bump spotbugs from 4.3.0 to 4.4.0
add 83f63e2 Merge branch 'pr-68'
add b214202 Bump checkstyle from 8.45.1 to 9.0
add f45ebc8 Merge pull request #69 from
apache/dependabot/maven/com.puppycrawl.tools-checkstyle-9.0
add f94a6cd Bump junit-vintage-engine from 5.7.2 to 5.8.0
add e410bc3 Bump maven-pmd-plugin from 3.14.0 to 3.15.0
add 82de08d Bump spotbugs from 4.4.0 to 4.4.1
add 0dbfe1d Bump maven.dependency.version from 3.8.1 to 3.8.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 (44ca37e)
\
N -- N -- N
refs/heads/dependabot/maven/maven.dependency.version-3.8.2 (0dbfe1d)
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:
pom.xml | 8 ++++----
src/changes/changes.xml | 7 ++++---
2 files changed, 8 insertions(+), 7 deletions(-)
