This is an automated email from the ASF dual-hosted git repository.

github-bot pushed a change to branch dependabot/maven/ver.micrometer-1.11.4
in repository https://gitbox.apache.org/repos/asf/jena.git


 discard dfca6d4229 Bump ver.micrometer from 1.11.3 to 1.11.4
     add 5f4204c0cb Bump actions/checkout from 3 to 4
     add b4ee13e99c Bump org.roaringbitmap:RoaringBitmap from 0.9.47 to 1.0.0
     add 6523fa5184 Bump ver.micrometer from 1.11.3 to 1.11.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   (dfca6d4229)
            \
             N -- N -- N   refs/heads/dependabot/maven/ver.micrometer-1.11.4 
(6523fa5184)

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:
 .github/workflows/maven.yml         | 2 +-
 .github/workflows/maven_macos.yml   | 2 +-
 .github/workflows/maven_windows.yml | 2 +-
 pom.xml                             | 2 +-
 4 files changed, 4 insertions(+), 4 deletions(-)

Reply via email to