Dependency conflict: gopkg.in/yaml.v3 vs go.yaml.in/yaml/v3 causes build failures

[mhd-riaz]

I'm encountering a build error in my project due to a dependency conflict between gopkg.in/yaml.v3 and go.yaml.in/yaml/v3. Many Go projects and dependencies are migrating to go.yaml.in/yaml/v3 since the original github.com/go-yaml/yaml repo is now archived and the canonical import path is go.yaml.in/yaml/v3.

However, github.com/labstack/echo/v4 (or its dependencies) still require gopkg.in/yaml.v3, which causes the following error during build:

This is because Go treats these as different modules, leading to type mismatches.

Request: Please update all dependencies and internal imports to use only go.yaml.in/yaml/v3 as the canonical YAML v3 package. This will help downstream users avoid module conflicts and build errors.

[softexpert]

Actually the recommended version would be v4 : go.yaml.in/yaml/v4