Alanxtl opened a new issue, #3582: URL: https://github.com/apache/dubbo-go/issues/3582
## Background The main module currently depends on `gopkg.in/yaml.v3 v3.0.1`, and several runtime/configuration paths import `gopkg.in/yaml.v3` directly. The repository already has partial usage of `go.yaml.in/yaml/v4` under `tools/protoc-gen-triple-openapi`, so it would be good to align the main codebase with the newer YAML module path. ## Scope Upgrade YAML usage from: ```go import "gopkg.in/yaml.v3" ``` to: ```go import "go.yaml.in/yaml/v4" ``` Affected areas include YAML parsing/encoding in: - config center - routing rules - REST config reader - Triple OpenAPI encoder - Getty remoting config - gRPC client config ## Tasks - Replace direct imports of `gopkg.in/yaml.v3` with `go.yaml.in/yaml/v4`. - Update `go.mod` and `go.sum`. - Remove obsolete direct YAML dependency entries where possible. - Check whether `gopkg.in/yaml.v2` / `gopkg.in/yaml.v3` remain only as transitive dependencies. - Run relevant unit tests for configuration parsing, router parsing, OpenAPI encoding, and protocol config paths. - Verify there are no behavior regressions in YAML marshal/unmarshal compatibility. ## Acceptance Criteria - Main module uses `go.yaml.in/yaml/v4` for direct YAML operations. - `go test ./...` passes, or any unrelated existing failures are documented. - Existing YAML-based Dubbo configuration files continue to parse successfully. - OpenAPI YAML output remains valid. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
