This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/spring6/org.easymock-easymock-5.1.0
in repository https://gitbox.apache.org/repos/asf/isis.git
discard 7e0043a521 Bump easymock from 5.0.1 to 5.1.0
add e410353dbe Bump dependency-check-maven from 7.4.1 to 7.4.3
add e155fb42ed Merge pull request #1312 from
apache/dependabot/maven/spring6/org.owasp-dependency-check-maven-7.4.3
add a407c208c1 Bump error_prone_annotations from 2.16 to 2.17.0
add 68718b635b Merge pull request #1318 from
apache/dependabot/maven/spring6/com.google.errorprone-error_prone_annotations-2.17.0
add ebf7392204 Bump easymock from 5.0.1 to 5.1.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 (7e0043a521)
\
N -- N -- N
refs/heads/dependabot/maven/spring6/org.easymock-easymock-5.1.0 (ebf7392204)
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:
bom/pom.xml | 2 +-
core/pom.xml | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
