Bump the other-go-modules group with 6 updates

[dependabot]

Bumps the other-go-modules group with 6 updates:

Package	From	To
github.com/containernetworking/plugins	1.6.1	1.6.2
github.com/k8snetworkplumbingwg/network-attachment-definition-client	1.7.0	1.7.6
github.com/onsi/gomega	1.36.2	1.36.3
gomodules.xyz/jsonpatch/v2	2.4.0	2.5.0
github.com/go-co-op/gocron/v2	2.12.4	2.16.1
golang.org/x/time	0.8.0	0.11.0

Updates github.com/containernetworking/plugins from 1.6.1 to 1.6.2

Release notes

Sourced from github.com/containernetworking/plugins's releases.

v1.6.2

(administrative note: release v1.6.1 was somehow double-created in GitHub; v1.6.2 is identical but fixes the duplication.)

What's Changed

• portmap: fix nftables backend by @​champtar in containernetworking/plugins#1116
• ipmasq: fix nftables backend by @​champtar in containernetworking/plugins#1120
• portmap: fix iptables conditions detection by @​champtar in containernetworking/plugins#1117

Full Changelog: containernetworking/plugins@v1.6.0...v1.6.2

Commits

• See full diff in compare view

Updates github.com/k8snetworkplumbingwg/network-attachment-definition-client from 1.7.0 to 1.7.6

Release notes

Sourced from github.com/k8snetworkplumbingwg/network-attachment-definition-client's releases.

v1.7.6

This release fixes a regression affecting CNI plugins that do not specify interfaces in their CNI ADD result.

Previously, IP addresses returned without an associated interface index were not being assigned to any network-status entry. This release restores the prior behavior by assigning such IPs to the last network status (i.e., the last sandboxed interface), ensuring consistent handling across plugins, especially those that omit the interfaces field entirely.

This change is important for compatibility with certain CNI plugins and maintains expected behavior from earlier versions of the net-attach-def library.

Special thanks to @​Brian-McM for identifying the issue and providing the fix!

v1.7.5

This release contains a fix related to the determination of the default interface, e.g. setting the default parameter to true in the network-status annotation based on the presence of a gateway in the CNI ADD success result ips.gateway and makes the determination of the default based on the first interface that has an associated value of gateway (using the interface index in the ips element in the CNI ADD success result).

This provides flexibility especially in CRI-O which uses the first interface and IP addresses for the pod.IP in Kubernetes, therefore. Containerd functionality is unchanged in that it uses the value for the IP addresses specifically

It's worth noting that CNI ADD success results which do not contain any interfaces will be discarded in this determination of the default, therefore it's recommended to set one with an associated gateway if aiming to have it be noted as the default.

v1.7.4

This release accounts for CNI plugins which do not use the sandbox field in results when calculating the network-status annotation, doing so for backwards compatibility for plugins which choose to not use this field (such as Calico)

v1.7.3

This release accounts for the sandox interfaces when reporting the interfaces in the network-status annotation; in case the CreateNetworkStatuses clients invoke it with a CNI result featuring non-sandbox interfaces as the first item in the list, this release accounts for that condition.

v1.7.2

When the CreateNetworkStatuses method was created to properly set the network-status annotation when a CNI result includes multiple interfaces in the return, it was found that it when setting the "default" parameter in the network-status, it was setting it to all the returned interfaces to true, which doesn't fit the NPWG net-attach-def specification.

This release fixes that issue by using the first interface in the CNI result set to "default": true for the cluster default network and not the following interfaces.

NOTE Do not use this version, use >= v1.7.3

v1.7.1

Adds the CreateNetworkStatuses method to properly set the network-status annotation when a CNI result includes multiple interfaces in the return.

For details of the before/after, see this gist: https://gist.github.com/dougbtv/1eb8ac2d61d494b56d65a6b236a86e61

For the related suggested update to the NPWG net-attach-def specification (for clarity only), see this proposal @ https://docs.google.com/document/d/1DUTV-o6E6zlRTKZkxeDhAeyGrmq03qPgPbU580Rm7-g/edit

Commits

• e12bd55 Merge pull request #77 from Brian-McM/assign-ips-with-no-interface-to-default...
• 77dfd49 Update pkg/utils/net-attach-def_test.go
• 1945b69 Assign IPs that don't have an interface index to the last network status
• 7d2def1 Merge pull request #73 from dougbtv/gw-for-default
• 55f81d3 Assigns default=true on a multiple interface return for first interface with ...
• 9b218a2 Merge pull request #72 from maiqueb/address-calico-not-defining-sandbox
• ed6baad Preserve backwards compatibility of CreateNetworkStatus
• 506cfda Merge pull request #71 from maiqueb/account-for-sandbox-ifaces-when-choosing-...
• d8782ff Accont for non-sandbox interfaces when specifying the default network
• d23f60f Merge pull request #70 from maiqueb/multiple-default-interfaces
• Additional commits viewable in compare view

Updates github.com/onsi/gomega from 1.36.2 to 1.36.3

Release notes

Sourced from github.com/onsi/gomega's releases.

v1.36.3

1.36.3

Maintenance

• bump all the things [adb8b49]
• chore: replace interface{} with any [7613216]
• Bump google.golang.org/protobuf from 1.36.1 to 1.36.5 (#822) [9fe5259]
• remove spurious "toolchain" from go.mod (#819) [a0e85b9]
• Bump golang.org/x/net from 0.33.0 to 0.35.0 (#823) [604a8b1]
• Bump activesupport from 6.0.6.1 to 6.1.7.5 in /docs (#772) [36fbc84]
• Bump github-pages from 231 to 232 in /docs (#778) [ced70d7]
• Bump rexml from 3.2.6 to 3.3.9 in /docs (#788) [c8b4a07]
• Bump github.com/onsi/ginkgo/v2 from 2.22.1 to 2.22.2 (#812) [06431b9]
• Bump webrick from 1.8.1 to 1.9.1 in /docs (#800) [b55a92d]
• Fix typos (#813) [a1d518b]

Changelog

Sourced from github.com/onsi/gomega's changelog.

1.36.3

Maintenance

• bump all the things [adb8b49]
• chore: replace interface{} with any [7613216]
• Bump google.golang.org/protobuf from 1.36.1 to 1.36.5 (#822) [9fe5259]
• remove spurious "toolchain" from go.mod (#819) [a0e85b9]
• Bump golang.org/x/net from 0.33.0 to 0.35.0 (#823) [604a8b1]
• Bump activesupport from 6.0.6.1 to 6.1.7.5 in /docs (#772) [36fbc84]
• Bump github-pages from 231 to 232 in /docs (#778) [ced70d7]
• Bump rexml from 3.2.6 to 3.3.9 in /docs (#788) [c8b4a07]
• Bump github.com/onsi/ginkgo/v2 from 2.22.1 to 2.22.2 (#812) [06431b9]
• Bump webrick from 1.8.1 to 1.9.1 in /docs (#800) [b55a92d]
• Fix typos (#813) [a1d518b]

Commits

• 2251143 v1.36.3
• adb8b49 bump all the things
• 7613216 chore: replace interface{} with any
• 9fe5259 Bump google.golang.org/protobuf from 1.36.1 to 1.36.5 (#822)
• a0e85b9 remove spurious "toolchain" from go.mod (#819)
• 604a8b1 Bump golang.org/x/net from 0.33.0 to 0.35.0 (#823)
• 36fbc84 Bump activesupport from 6.0.6.1 to 6.1.7.5 in /docs (#772)
• ced70d7 Bump github-pages from 231 to 232 in /docs (#778)
• c8b4a07 Bump rexml from 3.2.6 to 3.3.9 in /docs (#788)
• 06431b9 Bump github.com/onsi/ginkgo/v2 from 2.22.1 to 2.22.2 (#812)
• Additional commits viewable in compare view

Updates gomodules.xyz/jsonpatch/v2 from 2.4.0 to 2.5.0

Release notes

Sourced from gomodules.xyz/jsonpatch/v2's releases.

v2.5.0

What's Changed

• Fix: handle lossy max int64 by @​lacroixthomas in gomodules/jsonpatch#40

New Contributors

• @​lacroixthomas made their first contribution in gomodules/jsonpatch#40

Full Changelog: gomodules/jsonpatch@v2.4.0...v2.5.0

Commits

• ffbac60 Merge pull request #40 from lacroixthomas/bugfixes/fix-lossy-in64
• 4c723fc fix: handle lossy int64
• See full diff in compare view

Updates github.com/go-co-op/gocron/v2 from 2.12.4 to 2.16.1

Release notes

Sourced from github.com/go-co-op/gocron/v2's releases.

v2.16.1

What's Changed

• Fix #835 and #837 by @​apocelipes in go-co-op/gocron#836

Full Changelog: go-co-op/gocron@v2.16.0...v2.16.1

v2.16.0

What's Changed

• feat:custom-cron interface for own custom cron implimentation by @​Dojeto in go-co-op/gocron#834

Bug fixes

• fixes related to the bug where a job unexpectedly runs twice by @​JohnRoesler in go-co-op/gocron#810
• fix scheduler restart by @​27149chen in go-co-op/gocron#825
• removes nextRuns in the past when job skipped by locker #828 by @​manuelarte in go-co-op/gocron#829

Chores

• go to 1.21, upgrade deps by @​JohnRoesler in go-co-op/gocron#822
• replace "golang.org/x/exp" with standard libraries by @​apocelipes in go-co-op/gocron#823
• Bump golangci/golangci-lint-action from 6.2.0 to 6.3.2 by @​dependabot in go-co-op/gocron#827
• fix err assertion in TestScheduler_RemoveJob by @​alexandear in go-co-op/gocron#830
• Bump golangci/golangci-lint-action from 6.3.2 to 6.5.0 by @​dependabot in go-co-op/gocron#831
• re-enable goleak detection in ci by @​JohnRoesler in go-co-op/gocron#832
• chore: add go1.24 to ci by @​apocelipes in go-co-op/gocron#833

New Contributors

• @​alexandear made their first contribution in go-co-op/gocron#830
• @​Dojeto made their first contribution in go-co-op/gocron#834

Full Changelog: go-co-op/gocron@v2.15.0...v2.16.0

v2.15.0

What's New

• New method WithContext supports providing a parent context by @​27149chen in go-co-op/gocron#819 & @​JohnRoesler in go-co-op/gocron#820

// WithContext sets the parent context for the job.
// If you set the first argument of your Task func to be a context.Context,
// gocron will pass in the provided context to the job and will cancel the
// context on shutdown. If you cancel the context the job will no longer be
// scheduled as well. This allows you to both control the job via a context
// and listen for and handle cancellation within your job.

• Job task function now supports passing a ctx if the first argument in your function is a context.Context by @​27149chen in go-co-op/gocron#819 & @​JohnRoesler in go-co-op/gocron#820

// NewTask provides the job's task function and parameters.
// If you set the first argument of your Task func to be a context.Context,
// gocron will pass in a context (either the default Job context, or one
</tr></table> 

... (truncated)

Commits

• 63f3701 Fix #835 and #837 (#836)
• e1b7d52 ExampleWithCronImplementation
• 69b4347 clean up
• 36cd85f feat:custom-cron interface for own custom cron implimentation (#834)
• 1fe8c5c chore: add go1.24 to ci (#833)
• 2769f09 removes nextRuns in the past when job skipped by locker (#829)
• 08b53d7 re-enable goleak detection in ci (#832)
• 129f89c Bump golangci/golangci-lint-action from 6.3.2 to 6.5.0 (#831)
• 34fc56e fix err assertion in TestScheduler_RemoveJob (#830)
• 8998063 Bump golangci/golangci-lint-action from 6.2.0 to 6.3.2 (#827)
• Additional commits viewable in compare view

Updates golang.org/x/time from 0.8.0 to 0.11.0

Commits

• 0c50ed8 all: upgrade go directive to at least 1.23.0 [generated]
• 66520f6 rate: simplify function advance only returns new Tokens to caller
• 2c6c5a2 rate: prevent overflows when calculating durationFromTokens
• 1ce61fe rate: make function comment match function name
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.