This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/master/org.junit.jupiter-junit-jupiter-api-5.9.0
in repository https://gitbox.apache.org/repos/asf/isis.git
discard f583c627fe Bump junit-jupiter-api from 5.8.2 to 5.9.0
add 0e5fa1489f Bump graphql-java from 18.2 to 19.0
add 6c8861ecaa Merge pull request #1034 from
apache/dependabot/maven/master/com.graphql-java-graphql-java-19.0
add 9e7305a39d Bump junit-platform-console from 1.8.2 to 1.9.0
add 8421607b35 Merge pull request #1033 from
apache/dependabot/maven/master/org.junit.platform-junit-platform-console-1.9.0
add 85fa32d10b Bump junit-jupiter-api from 5.8.2 to 5.9.0
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 (f583c627fe)
\
N -- N -- N
refs/heads/dependabot/maven/master/org.junit.jupiter-junit-jupiter-api-5.9.0
(85fa32d10b)
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 +-
tooling/dsl/pom.xml | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
