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

ruifengz pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/spark.git


The following commit(s) were added to refs/heads/master by this push:
     new d9248e83bbb [SPARK-43974][CONNECT][BUILD] Upgrade buf to v1.23.1
d9248e83bbb is described below

commit d9248e83bbb3af49333608bebe7149b1aaeca738
Author: panbingkun <pbk1...@gmail.com>
AuthorDate: Wed Jul 12 18:32:24 2023 +0800

    [SPARK-43974][CONNECT][BUILD] Upgrade buf to v1.23.1
    
    ### What changes were proposed in this pull request?
    The pr aims to upgrade buf from 1.20.0 to 1.23.1
    
    ### Why are the changes needed?
    1.Release Notes:
    - https://github.com/bufbuild/buf/releases/tag/v1.23.1
    - https://github.com/bufbuild/buf/releases/tag/v1.23.0
    - https://github.com/bufbuild/buf/releases/tag/v1.22.0
    - https://github.com/bufbuild/buf/releases/tag/v1.21.0
    
    2.The new version brings some bug fixed and improvment, as follow:
    - Fix issue where buf beta graph would not print modules within a workspace 
that
    had no dependencies or dependents.
    - Fix issue where buf beta graph would print warnings for missing 
dependencies
    that were actually present.
    - Fix issue where locally-produced images did not have module information 
if the corresponding
    module was stored in the new cache.
    - Remove buf beta registry template.
    - Remove buf beta registry plugin 
{create,deprecate,list,undeprecate,version} and replace with
    buf beta registry plugin {push,delete}.
    - Update buf beta price with the latest pricing information.
    
    3.Manually test: dev/connect-gen-protos.sh, this upgrade will not change 
the generated files.
    
    ### Does this PR introduce _any_ user-facing change?
    No.
    
    ### How was this patch tested?
    - Manually test
    - Pass GA
    
    Closes #41937 from panbingkun/SPARK-43974_Right.
    
    Authored-by: panbingkun <pbk1...@gmail.com>
    Signed-off-by: Ruifeng Zheng <ruife...@apache.org>
---
 .github/workflows/build_and_test.yml            | 2 +-
 python/docs/source/development/contributing.rst | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/.github/workflows/build_and_test.yml 
b/.github/workflows/build_and_test.yml
index 186e7003aa2..0b184c6c248 100644
--- a/.github/workflows/build_and_test.yml
+++ b/.github/workflows/build_and_test.yml
@@ -631,7 +631,7 @@ jobs:
     - name: Install dependencies for Python code generation check
       run: |
         # See more in "Installation" 
https://docs.buf.build/installation#tarball
-        curl -LO 
https://github.com/bufbuild/buf/releases/download/v1.20.0/buf-Linux-x86_64.tar.gz
+        curl -LO 
https://github.com/bufbuild/buf/releases/download/v1.23.1/buf-Linux-x86_64.tar.gz
         mkdir -p $HOME/buf
         tar -xvzf buf-Linux-x86_64.tar.gz -C $HOME/buf --strip-components 1
         python3.9 -m pip install 'protobuf==3.19.5' 'mypy-protobuf==3.3.0'
diff --git a/python/docs/source/development/contributing.rst 
b/python/docs/source/development/contributing.rst
index 32ae440711b..fa7bf11f6da 100644
--- a/python/docs/source/development/contributing.rst
+++ b/python/docs/source/development/contributing.rst
@@ -120,7 +120,7 @@ Prerequisite
 
 PySpark development requires to build Spark that needs a proper JDK installed, 
etc. See `Building Spark 
<https://spark.apache.org/docs/latest/building-spark.html>`_ for more details.
 
-Note that if you intend to contribute to Spark Connect in Python, ``buf`` 
version ``1.20.0`` is required, see `Buf Installation 
<https://docs.buf.build/installation>`_ for more details.
+Note that if you intend to contribute to Spark Connect in Python, ``buf`` 
version ``1.23.1`` is required, see `Buf Installation 
<https://docs.buf.build/installation>`_ for more details.
 
 Conda
 ~~~~~


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@spark.apache.org
For additional commands, e-mail: commits-h...@spark.apache.org

Reply via email to