Skip to content

chore: switch to go.yaml.in/yaml/v3 - #974

Draft
thaJeztah wants to merge 2 commits into
prometheus:mainfrom
thaJeztah:bump_yaml
Draft

chore: switch to go.yaml.in/yaml/v3#974
thaJeztah wants to merge 2 commits into
prometheus:mainfrom
thaJeztah:bump_yaml

Conversation

@thaJeztah

Copy link
Copy Markdown
Contributor

chore: switch to go.yaml.in/yaml/v3

Use the more widely adopted yaml.v3 module, which is already present
as an indirect dependency through packages such as stretchr/testify.

Replace UnmarshalStrict with a decoder configured to reject unknown
fields, while continuing to accept empty configuration files. Keep the
callback-based UnmarshalYAML methods for compatibility with both yaml.v2
and yaml.v3, and update tests for yaml.v3's output formatting.

update testify to reduce indirect dependencies and to remove the
deprecated gopkg.in/yaml.v3 dependency.

Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
Use the more widely adopted yaml.v3 module, which is already present
as an indirect dependency through packages such as stretchr/testify.

Replace UnmarshalStrict with a decoder configured to reject unknown
fields, while continuing to accept empty configuration files. Keep the
callback-based UnmarshalYAML methods for compatibility with both yaml.v2
and yaml.v3, and update tests for yaml.v3's output formatting.

Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant