This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/com.github.spotbugs-spotbugs-maven-plugin-4.0.4
in repository https://gitbox.apache.org/repos/asf/commons-build-plugin.git.
discard edc9855 Bump spotbugs-maven-plugin from 4.0.0 to 4.0.4
add c310a9b Bump actions/checkout from v1 to v2.3.1
add 0acd127 Merge pull request #6 from
apache/dependabot/github_actions/actions/checkout-v2.3.1
add 8c4eda2 Bump commons-parent from 48 to 51
add 7a431d0 Merge pull request #4 from
apache/dependabot/maven/org.apache.commons-commons-parent-51
add 6cd840e Bump spotbugs-maven-plugin from 4.0.0 to 4.0.4
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 (edc9855)
\
N -- N -- N
refs/heads/dependabot/maven/com.github.spotbugs-spotbugs-maven-plugin-4.0.4
(6cd840e)
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:
.github/workflows/maven.yml | 2 +-
pom.xml | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
