This is an automated email from the ASF dual-hosted git repository.
dependabot[bot] pushed a change to branch
dependabot/maven/org.apache.commons-commons-parent-105
in repository https://gitbox.apache.org/repos/asf/commons-collections.git
omit 40c9714fc Bump org.apache.commons:commons-parent from 104 to 105
add 2d16db60e Bump com.google.guava:guava-testlib from 33.6.0-jre to
33.7.1-jre (#733)
add 4bb680bb7 Bump com.google.guava:guava-testlib from 33.6.0-jre to
33.7.1-jre (#733).
add 550bc3157 Bump org.easymock:easymock from 5.6.0 to 5.7.0 (#732)
add 9240a1ca3 Bump org.easymock:easymock from 5.6.0 to 5.7.0 (#732).
add bf04be9b3 Bump org.apache.commons:commons-parent from 104 to 105
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 (40c9714fc)
\
N -- N -- N
refs/heads/dependabot/maven/org.apache.commons-commons-parent-105 (bf04be9b3)
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 ++--
src/changes/changes.xml | 2 ++
2 files changed, 4 insertions(+), 2 deletions(-)
