[2025-10-25] Manual Dependency Bump

[joshjms]

Please read https://github.com/etcd-io/etcd/blob/main/CONTRIBUTING.md#contribution-flow.

This pull request completes this week's etcd dependency updates following our dependency roster and dependency management instructions.

Dependabot raised the following PRs:

Bumped

• build(deps): bump golang.org/x/net from 0.44.0 to 0.46.0 #20820
• build(deps): bump github.com/prometheus/common from 0.66.1 to 0.67.1 #20822
• build(deps): bump golang.org/x/tools from 0.37.0 to 0.38.0 in /tools/mod #20823
• build(deps): bump golang.org/x/time from 0.13.0 to 0.14.0 #20824
• build(deps): bump github.com/google/yamlfmt from 0.17.2 to 0.19.0 in /tools/mod #20825
• build(deps): bump golang.org/x/crypto from 0.42.0 to 0.43.0 #20827

Fully indirect

• build(deps): bump golang.org/x/text from 0.29.0 to 0.30.0 #20821

/cc @ivanvc @ahrtr @henrybear327

P.S. Thanks @henrybear327 for the update_dep.sh :D

[joshjms]

/retest

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 69.32%. Comparing base (bd7796b) to head (276097f).
⚠️ Report is 19 commits behind head on main.

Additional details and impacted files

see 22 files with indirect coverage changes

@@            Coverage Diff             @@
##             main   #20830      +/-   ##
==========================================
+ Coverage   69.15%   69.32%   +0.16%     
==========================================
  Files         422      422              
  Lines       34824    34824              
==========================================
+ Hits        24084    24141      +57     
+ Misses       9341     9296      -45     
+ Partials     1399     1387      -12     

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update bd7796b...276097f. Read the comment docs.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[ivanvc]

@joshjms, could you please run make fix? And commit again? Ideally, we should be committing the go.work.sum with every go.sum update, not as a separate commit. But while we adjust to this, it's fine to do it this way.

Thanks.

[joshjms]

I ran make fix before each commit :( when I run make fix again, nothing changes

[ivanvc]

Ah, @joshjms, I think an issue could be that the go module update runs before go mod tidy.

I checked out b3229b0, and then ran make fix, and there are changes to go.work.sum.

[joshjms]

I didn't see a b3229b0 commit :(

[joshjms]

@ivanvc Now go_workspace passes but the test still fails :(

[joshjms]

/retest

[ivanvc]

@joshjms, please take a look at #20839. I did what I mentioned, checked out each individual commit, and ran make fix. The verify job passes. You can use it as a reference, or if you'd like, I can take over your pull request.

[joshjms]

/retest

[ahrtr]

LGTM & thx

cc @ivanvc @jmhbnz

[ivanvc]

/retest

[ivanvc]

LGTM. Thanks, @joshjms.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ahrtr, ivanvc, joshjms

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [ahrtr,ivanvc]

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

[k8s-ci-robot]

@joshjms: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-etcd-coverage-report	276097f	link	true	/test pull-etcd-coverage-report

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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. I understand the commands that are listed here.