Merge branch 'cloudwego:main' into main

Author: meguminnnnnnnnn

.github/workflows/gh-page.yml

@@ -9,6 +9,8 @@ on:
 jobs:
   deploy:
     runs-on: ubuntu-latest
+    permissions:
+      contents: write
     steps:
       - uses: actions/checkout@v4
         with:

content/en/blog/releases/Kitex/release-v0_11_0.md

@@ -18,7 +18,6 @@ description: >
 1. **Frugal ARM Optimization**: Frugal v0.2.0 now supports a new implement by reflection
 2. **Kitex Tool Improvement**: Kitex Tool provide a new param `-rapid` to integrates Thriftgo and there's a slightly improved speed.
 3. **Generating Multiple Handlers for Multiple Services**：Since this version, Kitex tool provide each service with independent handler file and register them into server，for more details: [Generating Multiple Handlers for Multiple Services](/docs/kitex/tutorials/advanced-feature/multi_service/multi_handler/)
-4. **Generic Streaming for JSON [on trial]**：JSON generic streaming has now support streaming (client only)，currently we're doing some optimization, you can have a try by following this doc: [Generic Streaming](/docs/kitex/tutorials/advanced-feature/generic-call/generic_streaming/)
 
 
 ### Others

content/en/blog/releases/Kitex/release-v0_12_0.md

@@ -29,12 +29,6 @@ Future version plans: Kitex will remove Apache products by default. User guide:
    Added support for a graceful shutdown feature to address upstream errors caused by service upgrades or updates.
 
    For usage: [gRPC Streaming Graceful Shutdown](/docs/kitex/tutorials/basic-feature/protocol/streaming/grpc/graceful_shutdown/)
-   
-3. **JSON Generic Call Supports gRPC Streaming**
-   
-   JSON generic calls now support gRPC Streaming interfaces (client-side only). This is the official release after trial in v0.10.0.
-   
-   For usage: [User Guide to Generic Call for Streaming](/docs/kitex/tutorials/advanced-feature/generic-call/generic_streaming)
 
 ### Experience Optimization
 1. **gRPC Streaming Log Optimization**

content/en/blog/releases/Kitex/release-v0_14_0.md

@@ -0,0 +1,104 @@
+---
+title: "Kitex Release v0.14.0"
+linkTitle: "Release v0.14.0"
+projects: ["Kitex"]
+date: 2025-06-26
+description: >
+---
+
+## **Introduction to Key Changes**
+
+### **New Features**
+1. **Generic Call: The generic Client supports streaming calls, allowing a single Client to handle both streaming and non-streaming scenarios**
+
+   It supports streaming generic calls, adapting to gRPC/TTHeader Streaming and supporting map/JSON and Protobuf binary generic calls.
+
+   A brief code example is as follows:
+   ```go
+   cli, err := genericclient.NewClient("actualServiceName", g)
+   // Ping-Pong generic
+   resp, err := cli.GenericCall(ctx, "PingPongTest", req)
+   // ClientStreaming generic
+   cliStream, err := cli.ClientStreaming(ctx, "ClientStreamingTest")
+   // ServerStreaming generic
+   srvStream, err := cli.ServerStreaming(ctx, "ServerStreamingTest", req)
+   // BidiStreaming generic
+   bidiStream, err := cli.BidiStreaming(ctx, "BidiStreamingTest")
+   ```
+
+   Refer to this document for details: [Generic Call](/docs/kitex/tutorials/advanced-feature/generic-call/basic_usage).
+
+### **Feature/Experience Optimization**
+1. **Streaming: Improved observability and debugging experience**
+
+   **TTHeader Streaming**
+    - If Tracer configured, failure to create a stream will now be reported with metrics.
+    - When a panic occurs on the Server side, the full stack trace will now be printed for easier troubleshooting.
+
+   **gRPC Streaming**
+    - If Tracer configured, failure to create a stream will now be reported with metrics.
+
+### **Others**
+1. **Code Product Simplification**
+
+   Kitex tool no longer generates fastpb, only affecting Protobuf users.
+
+   If high-performance Protobuf encoding/decoding is required, you can enable prutal by configuring environment variable `KITEX_TOOL_USE_PRUTAL_MARSHAL=1`.
+
+## **Full Change**
+### Feature
+[[#1759](https://github.com/cloudwego/kitex/pull/1759)] feat(tool): add env for using prutal to marshal
+
+[[#1782](https://github.com/cloudwego/kitex/pull/1782)] feat(ttstream): process MetaFrame and reflect to rpcinfo
+
+[[#1777](https://github.com/cloudwego/kitex/pull/1777)] feat(client): report err when create Stream failed
+
+[[#1763](https://github.com/cloudwego/kitex/pull/1763)] feat: support ttheader streaming generic call
+
+[[#1771](https://github.com/cloudwego/kitex/pull/1771)] feat(tool): add thriftgo patcher extension
+
+[[#1755](https://github.com/cloudwego/kitex/pull/1755)] feat: add generic binary pb for streamx
+
+[[#1752](https://github.com/cloudwego/kitex/pull/1752)] feat(generic): support generic pb binary for streaming
+
+### Optimize
+[[#1788](https://github.com/cloudwego/kitex/pull/1788)] optimize: go net implementation
+
+[[#1786](https://github.com/cloudwego/kitex/pull/1786)] optimize(tool): remove tool fastpb generation
+
+[[#1783](https://github.com/cloudwego/kitex/pull/1783)] optimize(gRPC): parse PayloadCodec in server side
+
+[[#1780](https://github.com/cloudwego/kitex/pull/1780)] optimize(ttstream): log the error thrown by invoking handler
+
+[[#1769](https://github.com/cloudwego/kitex/pull/1769)] optimize: injection of options in ttstream
+
+### Fix
+[[#1792](https://github.com/cloudwego/kitex/pull/1792)] fix(gRPC): inject current method name to rpcinfo in server-side to fix FROM_METHOD missing
+
+[[#1787](https://github.com/cloudwego/kitex/pull/1787)] fix(ttstream): metrics missing caused by server-side rpcinfo not set correctly
+
+[[#1778](https://github.com/cloudwego/kitex/pull/1778)] fix: enabling json mode of map generic not work
+
+[[#1774](https://github.com/cloudwego/kitex/pull/1774)] fix(server): trans server conn count race issue
+
+[[#1742](https://github.com/cloudwego/kitex/pull/1742)] fix(generic): align dynamicgo's write base behavior with old generic (only for internal logic)
+
+### Refactor
+[[#1770](https://github.com/cloudwego/kitex/pull/1770)] refactor: refactor generic streaming
+
+### Test
+[[#1793](https://github.com/cloudwego/kitex/pull/1793)] test: add go1.18 to scenario-test
+
+[[#1765](https://github.com/cloudwego/kitex/pull/1765)] refactor: refactor generic streaming
+
+### Docs
+[[#1794](https://github.com/cloudwego/kitex/pull/1794)] docs: update CONTRIBUTING.md to change PR base branch to main
+
+### Chore
+[[#1795](https://github.com/cloudwego/kitex/pull/1795)] chore: update dependency
+
+[[#1776](https://github.com/cloudwego/kitex/pull/1776)] chore: remove testify dependency
+
+[[#1757](https://github.com/cloudwego/kitex/pull/1757)] chore: update prutal to v0.1.1
+
+[[#1753](https://github.com/cloudwego/kitex/pull/1753)] ci: disable codecov annotations

content/en/docs/eino/overview/_index.md

@@ -199,7 +199,7 @@ compiledGraph.Invoke(ctx, input, WithCallbacks(handler).DesignateNode("node_1"))
 
 ## Eino framework structure
 
-<a href="/img/eino/eino_projects_and_structure.png" target="_blank"><img src="/img/eino/eino_projects_and_structure.png" width="100%" /></a>
+<a href="/img/eino/eino_structure.png" target="_blank"><img src="/img/eino/eino_structure.png" width="100%" /></a>
 
 The Eino framework consists of several parts:
 

content/en/docs/hertz/tutorials/basic-feature/sse.md

@@ -83,6 +83,10 @@ func HandleSSE(ctx context.Context, resp *protocol.Response) error {
 }
 ```
 
+### Example Codes
+
+- [SSE](https://github.com/cloudwego/hertz-examples/tree/main/sse) : Example of hertz using SSE protocol
+
 ### Common Issues
 
 #### How to implement multi-level SSE / SSE Proxy?

content/en/docs/hertz/tutorials/example/_index.md

@@ -51,7 +51,7 @@ Hertz provides a series of code examples designed to help users get start with H
 - [HTTP2](https://github.com/hertz-contrib/http2/tree/main/examples) : Example of hertz using HTTP2 protocol
 - [HTTP3](https://github.com/hertz-contrib/http3/tree/main/examples/quic-go) : Example of hertz using HTTP3 protocol
 - [Websocket](https://github.com/hertz-contrib/websocket/tree/main/examples) : Example of hertz using Websocket protocol
-- [SSE](https://github.com/hertz-contrib/sse/tree/main/examples) : Example of hertz using SSE protocol
+- [SSE](https://github.com/cloudwego/hertz-examples/tree/main/sse) : Example of hertz using SSE protocol
 
 ### Route
 

content/en/docs/hertz/tutorials/framework-exten/response_writer.md

@@ -10,8 +10,7 @@ description: "Response Writer Extension provided by Hertz."
 According to Hertz's [layered architecture](/zh/docs/hertz/overview/), the actual write
 operation of the HTTP response is performed after the application layer user processing logic returns. Under this
 constraint, users cannot flexibly control the behavior of write operations on demand. This limitation is especially
-obvious in scenarios such as controlling chunked encoding write logic
-and [SSE](https://github.com/hertz-contrib/sse#hertz-sse).
+obvious in scenarios such as controlling chunked encoding write logic.
 
 To solve this problem, Hertz provides an extension called "Response Writer Hijacking" that can vertically penetrate the
 limitations brought by the layered architecture in an orthogonal way. It allows users to freely customize the logic of

content/en/docs/hertz/tutorials/observability/log.md

@@ -18,7 +18,7 @@ func AccessLog() app.HandlerFunc {
 		start := time.Now()
 		c.Next(ctx)
 		end := time.Now()
-		latency := end.Sub(start).Microseconds
+		latency := end.Sub(start).Microseconds()
 		hlog.CtxTracef(ctx, "status=%d cost=%d method=%s full_path=%s client_ip=%s host=%s",
 			c.Response.StatusCode(), latency,
 			c.Request.Header.Method(), c.Request.URI().PathOriginal(), c.ClientIP(), c.Request.Host())

content/en/docs/hertz/tutorials/third-party/protocol/_index.md

@@ -2,7 +2,7 @@
 title: "Protocol"
 date: 2022-05-23
 weight: 1
-keywords: ["Websocket", "HTTP2", "HTTP3", "SSE"]
+keywords: ["TLS", "ALPN", "Websocket", "HTTP2", "HTTP3"]
 description: "Protocol extensions supported by Hertz."
 ---
 
@@ -17,7 +17,3 @@ Hertz references [net/http2](https://github.com/golang/net/tree/master/http2) to
 ## HTTP3
 
 Hertz reference [quic-go](https://github.com/quic-go/quic-go) to implement support for HTTP3.
-
-## SSE
-
-Hertz supports SSE, allowing the server to send events to the client through simple HTTP response.