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 ecc07ed3eb Bump datanucleus-jodatime from 6.0.0-m5 to 6.0.0-release add 103d68b139 Bump datanucleus-api-jdo from 6.0.0-m5 to 6.0.0-release add efc0d20498 Merge pull request #998 from apache/dependabot/maven/master/org.datanucleus-datanucleus-api-jdo-6.0.0-release add f8a0aa1205 Bump datanucleus-jdo-query from 6.0.0-m1 to 6.0.0-release add 88d1c993ee Merge pull request #1002 from apache/dependabot/maven/master/org.datanucleus-datanucleus-jdo-query-6.0.0-release add a55377cdf9 Bump datanucleus-rdbms from 6.0.0-m5 to 6.0.0-release add b581b45590 Merge pull request #1001 from apache/dependabot/maven/master/org.datanucleus-datanucleus-rdbms-6.0.0-release add c35d983a51 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 (ecc07ed3eb) \ N -- N -- N refs/heads/dependabot/maven/master/org.datanucleus-datanucleus-jodatime-6.0.0-release (c35d983a51) 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 +- 2 files changed, 4 insertions(+), 4 deletions(-)