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
discard c35d983a51 Bump datanucleus-jodatime from 6.0.0-m5 to 6.0.0-release
add b1cfc27dc4 Bump datanucleus-api-jpa from 6.0.0-m5 to 6.0.0-release
add bac8987b96 Merge pull request #1003 from
apache/dependabot/maven/master/org.datanucleus-datanucleus-api-jpa-6.0.0-release
add cadef92d40 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 (c35d983a51)
\
N -- N -- N
refs/heads/dependabot/maven/master/org.datanucleus-datanucleus-jodatime-6.0.0-release
(cadef92d40)
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 +-
1 file changed, 1 insertion(+), 1 deletion(-)
