==> /opt/conda/bin/git log -n1 <==
commit 12235e24652fc7f809373e7c11a5f73c5763fc4c
Author: Dominic Hamon <dominic+github@google.com>
Date:   Fri Aug 16 11:08:15 2024 +0100

    v1.9.0
==> /opt/conda/bin/git describe --tags --dirty <==
v1.9.0
==> /opt/conda/bin/git status <==
HEAD detached at 12235e24
nothing to commit, working tree clean
==> /opt/conda/bin/git log -n1 <==
commit 4de3c74cf21a9958c1cf26d8993c55c6e0d28b49
Author: update-envoy[bot] <135279899+update-envoy[bot]@users.noreply.github.com>
Date:   Tue Jan 28 16:14:02 2025 +0000

    support backoff between retries in tcp_proxy (#37709)
    
    Commit Message: support backoff between retries in tcp_proxy
    Additional Description: This feature also fixes a bug in the retry
    mechanism in tcp proxy in the following situation:
    1. We are tunneling TCP over HTTP.
    2. A new stream is created on existing upstream connection
    (multiplexing) and waiting for response headers.
    3. The upstream connection is closed.
    4. During the close process, all streams created on this connection will
    be reset.
    5. The tcp_proxy receives a callback on the stream reset.
    6. They retry to connect.
    7. The closed connection is picked as it is still in the connection pool
    (we are still in the process of the close).
    8. The new stream that is created on the second attempt will be reset
    immediately.
    9. The same process will happen (step 5 - step 8) until we reach the
    max_connect_attepts.
    10. This means that we are doing only one real attempt in this
    situation.
    
    Risk Level: medium
    Testing: unit tests, integration tests
    Docs Changes: added
    Release Notes: added
    
    ---------
    
    Signed-off-by: Issa Abu Kalbein <iabukalbein@microsoft.com>
    Signed-off-by: IssaAbuKalbein <86603440+IssaAbuKalbein@users.noreply.github.com>
    Co-authored-by: Issa Abu Kalbein <iabukalbein@microsoft.com>
    
    Mirrored from https://github.com/envoyproxy/envoy @ 7fa09db1c8cb5e99dc3808d69e7d83276aa9e240
==> /opt/conda/bin/git describe --tags --dirty <==
commit 4de3c74cf21a9958c1cf26d8993c55c6e0d28b49
Author: update-envoy[bot] <135279899+update-envoy[bot]@users.noreply.github.com>
Date:   Tue Jan 28 16:14:02 2025 +0000

    support backoff between retries in tcp_proxy (#37709)
    
    Commit Message: support backoff between retries in tcp_proxy
    Additional Description: This feature also fixes a bug in the retry
    mechanism in tcp proxy in the following situation:
    1. We are tunneling TCP over HTTP.
    2. A new stream is created on existing upstream connection
    (multiplexing) and waiting for response headers.
    3. The upstream connection is closed.
    4. During the close process, all streams created on this connection will
    be reset.
    5. The tcp_proxy receives a callback on the stream reset.
    6. They retry to connect.
    7. The closed connection is picked as it is still in the connection pool
    (we are still in the process of the close).
    8. The new stream that is created on the second attempt will be reset
    immediately.
    9. The same process will happen (step 5 - step 8) until we reach the
    max_connect_attepts.
    10. This means that we are doing only one real attempt in this
    situation.
    
    Risk Level: medium
    Testing: unit tests, integration tests
    Docs Changes: added
    Release Notes: added
    
    ---------
    
    Signed-off-by: Issa Abu Kalbein <iabukalbein@microsoft.com>
    Signed-off-by: IssaAbuKalbein <86603440+IssaAbuKalbein@users.noreply.github.com>
    Co-authored-by: Issa Abu Kalbein <iabukalbein@microsoft.com>
    
    Mirrored from https://github.com/envoyproxy/envoy @ 7fa09db1c8cb5e99dc3808d69e7d83276aa9e240
==> /opt/conda/bin/git status <==
HEAD detached at 4de3c74c
nothing to commit, working tree clean
==> /opt/conda/bin/git log -n1 <==
commit fe8ba054ad4f7eca946c2d14a63c3f07c0b586a0
Author: Google APIs <noreply@google.com>
Date:   Mon Aug 19 07:43:31 2024 -0700

    fix(deps): Update the Java code generator (gapic-generator-java) to 2.44.0
    
    PiperOrigin-RevId: 664804097
==> /opt/conda/bin/git describe --tags --dirty <==
common-protos-1_3_1-8757-gfe8ba054ad
==> /opt/conda/bin/git status <==
HEAD detached at fe8ba054ad
nothing to commit, working tree clean
==> /opt/conda/bin/git log -n1 <==
commit 52eb8108c5bdec04579160ae17225d66034bd723
Author: Derek Mauro <761129+derekmauro@users.noreply.github.com>
Date:   Wed Apr 30 12:54:29 2025 -0400

    Prepare for v1.17.0 (#4757)
==> /opt/conda/bin/git describe --tags --dirty <==
v1.17.0
==> /opt/conda/bin/git status <==
HEAD detached at 52eb8108
nothing to commit, working tree clean
==> /opt/conda/bin/git log -n1 <==
commit 7b06248484ceeaa947e93ca2747eccf336a88ecc
Author: Stefan VanBuren <svanburen@buf.build>
Date:   Wed Jan 22 15:15:32 2025 -0500

    Fix Python3.9 build (#1232)
    
    This fixes the python3.9 build by installing the pip requirements with
    python3.9 and ensuring python3.9-venv is installed.
    
    Follow up to #1225.
==> /opt/conda/bin/git describe --tags --dirty <==
v1.2.1
==> /opt/conda/bin/git status <==
HEAD detached at 7b062484
nothing to commit, working tree clean
==> /opt/conda/bin/git log -n1 <==
commit 3a472e524827f72d1ad621c4983dd5af54c46776
Author: Sergii Tkachenko <sergiitk@google.com>
Date:   Thu Nov 16 06:28:03 2023 -0800

    bazel: Migrate py_proto_library to `@com_github_grpc_grpc` (#74)
    
    py_proto_library provided by @com_google_protobuf//:protobuf.bzl has been deprecated for a while now:
    
    This is provided for backwards compatibility only. Bazel 5.3 will
    introduce support for py_proto_library, which should be used instead.
    https://github.com/protocolbuffers/protobuf/blob/32af7d211b85f71920acdfa9b796db008f8c2a45/protobuf.bzl#L642-L644
    
    However, native py_proto_library has never been provided, see bazelbuild/bazel#3935. Instead @rules_python//python:proto.bzl is recommended. I attempted switching to this library, but it's not compatible with @com_google_googleapis's py_proto_library targets, see #69. I found a hacky workaround by using cc_proto_library to generate python targets, but downstream integration into Envoy failed (envoyproxy/envoy#30159).
    
    This PR migrates py_proto_library implementation to to @com_github_grpc_grpc. This implementation is used by @com_google_googleapis's, and, more importantly, uses bazel aspects. Which decouples cncf/xds and Envoy's dependencies from concrete upstream py_proto_library implementations.
    
    This resulted in a significant code improvement of bazel/api_build_system.bzl:
    
    No more custom @com_google_googleapis dependency mapping needed via py_proto_library rules override.
    No more hardcoded dependencies _xds_py_proto_library - proto dependency tree is determined from proto_library definitions via Basel aspects.
    No more EXTERNAL_PROTO_PY_BAZEL_DEP_MAP dependency map needed - for the same reason.
    Similar work in Envoy: envoyproxy/envoy#30834.
    
    Signed-off-by: Sergii Tkachenko <sergiitk@google.com>
==> /opt/conda/bin/git describe --tags --dirty <==
commit 3a472e524827f72d1ad621c4983dd5af54c46776
Author: Sergii Tkachenko <sergiitk@google.com>
Date:   Thu Nov 16 06:28:03 2023 -0800

    bazel: Migrate py_proto_library to `@com_github_grpc_grpc` (#74)
    
    py_proto_library provided by @com_google_protobuf//:protobuf.bzl has been deprecated for a while now:
    
    This is provided for backwards compatibility only. Bazel 5.3 will
    introduce support for py_proto_library, which should be used instead.
    https://github.com/protocolbuffers/protobuf/blob/32af7d211b85f71920acdfa9b796db008f8c2a45/protobuf.bzl#L642-L644
    
    However, native py_proto_library has never been provided, see bazelbuild/bazel#3935. Instead @rules_python//python:proto.bzl is recommended. I attempted switching to this library, but it's not compatible with @com_google_googleapis's py_proto_library targets, see #69. I found a hacky workaround by using cc_proto_library to generate python targets, but downstream integration into Envoy failed (envoyproxy/envoy#30159).
    
    This PR migrates py_proto_library implementation to to @com_github_grpc_grpc. This implementation is used by @com_google_googleapis's, and, more importantly, uses bazel aspects. Which decouples cncf/xds and Envoy's dependencies from concrete upstream py_proto_library implementations.
    
    This resulted in a significant code improvement of bazel/api_build_system.bzl:
    
    No more custom @com_google_googleapis dependency mapping needed via py_proto_library rules override.
    No more hardcoded dependencies _xds_py_proto_library - proto dependency tree is determined from proto_library definitions via Basel aspects.
    No more EXTERNAL_PROTO_PY_BAZEL_DEP_MAP dependency map needed - for the same reason.
    Similar work in Envoy: envoyproxy/envoy#30834.
    
    Signed-off-by: Sergii Tkachenko <sergiitk@google.com>
==> /opt/conda/bin/git status <==
HEAD detached at 3a472e5
nothing to commit, working tree clean
