This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/spring6/org.datanucleus-datanucleus-rdbms-6.0.4
in repository https://gitbox.apache.org/repos/asf/causeway.git
discard cc5e3dc61f Bump datanucleus-rdbms from 6.0.3 to 6.0.4
add 5012651b55 Bump apache-source-release-assembly-descriptor from 1.0.6
to 1.5
add 2f59f026af Merge pull request #1566 from
apache/dependabot/maven/spring6/org.apache.apache.resources-apache-source-release-assembly-descriptor-1.5
add 4bad7ba26b Bump datanucleus-jodatime from 6.0.0-release to 6.0.1
add 34299a7f6b Merge pull request #1563 from
apache/dependabot/maven/spring6/org.datanucleus-datanucleus-jodatime-6.0.1
add 4dbb75e76a 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 (cc5e3dc61f)
\
N -- N -- N
refs/heads/dependabot/maven/spring6/org.datanucleus-datanucleus-rdbms-6.0.4
(4dbb75e76a)
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(-)
