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

github-bot pushed a change to branch 
dependabot/gradle/org.apache.beam-beam-runners-direct-java-2.45.0
in repository https://gitbox.apache.org/repos/asf/beam-starter-java.git


    omit 78de88a  Bump org.apache.beam:beam-runners-direct-java from 2.44.0 to 
2.45.0
     add 06bcac5  Bump beam-sdks-java-core from 2.44.0 to 2.45.0
     add ed28250  Merge pull request #48 from 
apache/dependabot/maven/org.apache.beam-beam-sdks-java-core-2.45.0
     add 2a1b119  Bump org.apache.beam:beam-sdks-java-core from 2.44.0 to 2.45.0
     add 68b986c  Merge pull request #45 from 
apache/dependabot/gradle/org.apache.beam-beam-sdks-java-core-2.45.0
     add 8de2bf4  Bump org.apache.beam:beam-runners-direct-java from 2.44.0 to 
2.45.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   (78de88a)
            \
             N -- N -- N   
refs/heads/dependabot/gradle/org.apache.beam-beam-runners-direct-java-2.45.0 
(8de2bf4)

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:
 build.gradle | 2 +-
 pom.xml      | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

Reply via email to