This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/master/org.datanucleus-datanucleus-jodatime-6.0.0-release
in repository https://gitbox.apache.org/repos/asf/isis.git
omit 7effb5beda Bump datanucleus-jodatime from 6.0.0-m5 to 6.0.0-release
add 78b7ac6dca Bump wagon-ftp from 3.5.1 to 3.5.2
add 1c869043c9 Merge pull request #999 from
apache/dependabot/maven/master/org.apache.maven.wagon-wagon-ftp-3.5.2
add de5ccae4a7 Bump graphql-java from 18.1 to 18.2
add 8d1a7c2668 Merge pull request #997 from
apache/dependabot/maven/master/com.graphql-java-graphql-java-18.2
add 100e77a6db Bump wagon-ssh from 3.5.1 to 3.5.2
add 469091fc4d Merge pull request #1000 from
apache/dependabot/maven/master/org.apache.maven.wagon-wagon-ssh-3.5.2
add c82efaeac7 Bump datanucleus-core from 6.0.0-m5 to 6.0.0-release
add 70f6b9e5d1 Merge pull request #995 from
apache/dependabot/maven/master/org.datanucleus-datanucleus-core-6.0.0-release
add 2a00064ae2 Bump datanucleus-jodatime from 6.0.0-m5 to 6.0.0-release
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 (7effb5beda)
\
N -- N -- N
refs/heads/dependabot/maven/master/org.datanucleus-datanucleus-jodatime-6.0.0-release
(2a00064ae2)
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 | 6 +++---
starters/pom.xml | 2 +-
tooling/dsl/pom.xml | 2 +-
3 files changed, 5 insertions(+), 5 deletions(-)
