Skip to content

Conversation

@SaschaSchwarze0
Copy link
Contributor

@SaschaSchwarze0 SaschaSchwarze0 commented Jan 22, 2026

  • 🧹 This replaces the unmaintained gopkg.in/yaml.v3 library with its maintained fork go.yaml.in/yaml/v3 from https://github.com/yaml/go-yaml/tree/v3/. It stays as indirect dependency due to flect and go-openapi, but anyway, one step further to eliminate it.
  • 🧹 This updates github.com/influxdata/influxdb-client-go/v2 from v2.9.0 to v2.14.0 which eliminates the indirect dependency on gopkg.in/yaml.v2

/kind cleanup

Release Note

None

Docs

None

Signed-off-by: Sascha Schwarze <schwarzs@de.ibm.com>
@knative-prow knative-prow bot added the kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. label Jan 22, 2026
@knative-prow knative-prow bot requested review from dprotaso, linkvt and skonto January 22, 2026 09:57
@knative-prow knative-prow bot added needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Jan 22, 2026
@knative-prow
Copy link

knative-prow bot commented Jan 22, 2026

Hi @SaschaSchwarze0. Thanks for your PR.

I'm waiting for a knative member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@SaschaSchwarze0 SaschaSchwarze0 marked this pull request as draft January 22, 2026 09:59
@knative-prow knative-prow bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 22, 2026
@linkvt
Copy link
Contributor

linkvt commented Jan 22, 2026

/ok-to-test

@knative-prow knative-prow bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Jan 22, 2026
@codecov
Copy link

codecov bot commented Jan 22, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 80.20%. Comparing base (36ccae0) to head (69ad59f).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main   #16352      +/-   ##
==========================================
+ Coverage   80.15%   80.20%   +0.05%     
==========================================
  Files         216      216              
  Lines       13440    13440              
==========================================
+ Hits        10773    10780       +7     
+ Misses       2301     2297       -4     
+ Partials      366      363       -3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

…14.0 to eliminate dependency on gopkg.in/yaml.v2

Signed-off-by: Sascha Schwarze <schwarzs@de.ibm.com>
@knative-prow knative-prow bot added size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Jan 22, 2026
@SaschaSchwarze0 SaschaSchwarze0 changed the title Replace gopkg.in/yaml.v3 with go.yaml.in/yaml/v3 Reduce gopkg.in/yaml usage Jan 22, 2026
@SaschaSchwarze0 SaschaSchwarze0 marked this pull request as ready for review January 22, 2026 10:11
@knative-prow knative-prow bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 22, 2026
@linkvt
Copy link
Contributor

linkvt commented Jan 22, 2026

/lgtm

Thanks, looks good!
One of the maintainers still has to approve to get this PR merged.

@knative-prow knative-prow bot added the lgtm Indicates that a PR is ready to be merged. label Jan 22, 2026
@dprotaso
Copy link
Member

/lgtm
/approve

@knative-prow
Copy link

knative-prow bot commented Jan 22, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dprotaso, SaschaSchwarze0

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@knative-prow knative-prow bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 22, 2026
@knative-prow knative-prow bot merged commit f692621 into knative:main Jan 22, 2026
94 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants