[causeway] branch dependabot/maven/master/com.structurizr-structurizr-core-1.19.0 updated (2b23f45888 -> f43fc4e21a)

[gi...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

github-bot pushed a change to branch dependabot/maven/master/com.structurizr-structurizr-core-1.19.0
in repository https://gitbox.apache.org/repos/asf/causeway.git


 discard 2b23f45888 Bump structurizr-core from 1.18.0 to 1.19.0
     add e9a826fb4d Bump dependency-check-maven from 8.0.1 to 8.0.2
     add f863878e7a Merge pull request #1387 from apache/dependabot/maven/master/org.owasp-dependency-check-maven-8.0.2
     add d10387d7b9 Bump picocli from 4.7.0 to 4.7.1
     add 97d72dd2c9 Merge pull request #1389 from apache/dependabot/maven/master/info.picocli-picocli-4.7.1
     add f43fc4e21a Bump structurizr-core from 1.18.0 to 1.19.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   (2b23f45888)
            \
             N -- N -- N   refs/heads/dependabot/maven/master/com.structurizr-structurizr-core-1.19.0 (f43fc4e21a)

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:
 core/pom.xml    | 2 +-
 tooling/pom.xml | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)