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-rdbms-6.0.4
in repository https://gitbox.apache.org/repos/asf/causeway.git
discard eaf6e8a2b5 Bump datanucleus-rdbms from 6.0.3 to 6.0.4
add 228f5eb3bb Bump apache-source-release-assembly-descriptor from 1.0.6
to 1.5
add f2fbee27b6 Merge pull request #1570 from
apache/dependabot/maven/master/org.apache.apache.resources-apache-source-release-assembly-descriptor-1.5
add 0639e99e4e Bump datanucleus-jodatime from 6.0.0-release to 6.0.1
add 87ca274a89 Merge pull request #1567 from
apache/dependabot/maven/master/org.datanucleus-datanucleus-jodatime-6.0.1
add 18b5b29c66 Bump datanucleus-rdbms from 6.0.3 to 6.0.4
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 (eaf6e8a2b5)
\
N -- N -- N
refs/heads/dependabot/maven/master/org.datanucleus-datanucleus-rdbms-6.0.4
(18b5b29c66)
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 | 4 ++--
starters/pom.xml | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
