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.6.0.0
in repository https://gitbox.apache.org/repos/asf/commons-jexl.git
omit aa7a70d6 Bump spotbugs-maven-plugin from 4.5.3.0 to 4.6.0.0
add 245e073c Bump jacoco-maven-plugin from 0.8.7 to 0.8.8
add fdba67bb Merge pull request #84 from
apache/dependabot/maven/org.jacoco-jacoco-maven-plugin-0.8.8
add 79d982aa Bump commons-parent from 52 to 53
add 48f5f46c Merge pull request #87 from
apache/dependabot/maven/org.apache.commons-commons-parent-53
add f95c293b Bump spotbugs-maven-plugin from 4.5.3.0 to 4.6.0.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 (aa7a70d6)
\
N -- N -- N
refs/heads/dependabot/maven/com.github.spotbugs-spotbugs-maven-plugin-4.6.0.0
(f95c293b)
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 | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
