chore(deps): bump the dependencies group across 2 directories with 1 update

[dependabot]

Bumps the dependencies group with 1 update in the /internal/cluster directory: go.sia.tech/coreutils.
Bumps the dependencies group with 1 update in the /sdk directory: go.sia.tech/coreutils.

Updates go.sia.tech/coreutils from 0.16.5-0.20250701190511-6ece69f09f12 to 0.16.5

Release notes

Sourced from go.sia.tech/coreutils's releases.

0.16.5 (2025-07-07)

Features

• Remove RedistributeV1|2 in favour of Redistribute. Return the index so the caller can use it as the basis when broadcasting the transactions.

Fixes

• Remove faulty utxo release, it is redundant since we lock utxos as the final step.
• Use only confirmed UTXOs for contract formation and renewals.

Changelog

Sourced from go.sia.tech/coreutils's changelog.

0.16.5 (2025-07-07)

Features

• Remove RedistributeV1|2 in favour of Redistribute. Return the index so the caller can use it as the basis when broadcasting the transactions.

Fixes

• Remove faulty utxo release, it is redundant since we lock utxos as the final step.
• Use only confirmed UTXOs for contract formation and renewals.

0.16.4 (2025-07-01)

Fixes

• Fix incorrect ordering of contract expirations preventing a consensus resync from scratch

0.16.3 (2025-06-19)

Features

• Require peers to support V2.

Fixes

• Increase default MaxInflightRPCs
• prevent reverted coinbase transactions from spamming the transaction pool
• Update core to v0.14.0

0.16.2 (2025-06-17)

Fixes

• Fixed an issue with a single syncing peer from taking over the sync loop.

Don't ignore missing supplement in updateV2TransactionProofs

##265 by @​lukechampine

The logic introduced in #193 caused a panic when a block supplement was missing: we would create an empty supplement, try to use it, then panic with out-of-range when trying to fetch stuff from the empty supplement.

In case you're wondering how we could end up in a situation where we have a block, but not a supplement: the supplement is only calculated when we fully validate and apply the block. If we receive a block that isn't on the best chain, we'll store it without also computing and storing the supplement. If someone then calls V2TransactionSet with a basis referencing that block, we'll attempt to use it.

0.16.1 (2025-06-14)

Fixes

• Added defer recover to prevent nodes from panicking due to uncaught bugs.
• Fixed a panic when attempting to update element proofs.
• Update core to v0.13.2

... (truncated)

Commits

• See full diff in compare view

Updates go.sia.tech/coreutils from 0.16.5-0.20250701190511-6ece69f09f12 to 0.16.5

Release notes

Sourced from go.sia.tech/coreutils's releases.

0.16.5 (2025-07-07)

Features

• Remove RedistributeV1|2 in favour of Redistribute. Return the index so the caller can use it as the basis when broadcasting the transactions.

Fixes

• Remove faulty utxo release, it is redundant since we lock utxos as the final step.
• Use only confirmed UTXOs for contract formation and renewals.

Changelog

Sourced from go.sia.tech/coreutils's changelog.

0.16.5 (2025-07-07)

Features

• Remove RedistributeV1|2 in favour of Redistribute. Return the index so the caller can use it as the basis when broadcasting the transactions.

Fixes

• Remove faulty utxo release, it is redundant since we lock utxos as the final step.
• Use only confirmed UTXOs for contract formation and renewals.

0.16.4 (2025-07-01)

Fixes

• Fix incorrect ordering of contract expirations preventing a consensus resync from scratch

0.16.3 (2025-06-19)

Features

• Require peers to support V2.

Fixes

• Increase default MaxInflightRPCs
• prevent reverted coinbase transactions from spamming the transaction pool
• Update core to v0.14.0

0.16.2 (2025-06-17)

Fixes

• Fixed an issue with a single syncing peer from taking over the sync loop.

Don't ignore missing supplement in updateV2TransactionProofs

##265 by @​lukechampine

The logic introduced in #193 caused a panic when a block supplement was missing: we would create an empty supplement, try to use it, then panic with out-of-range when trying to fetch stuff from the empty supplement.

In case you're wondering how we could end up in a situation where we have a block, but not a supplement: the supplement is only calculated when we fully validate and apply the block. If we receive a block that isn't on the best chain, we'll store it without also computing and storing the supplement. If someone then calls V2TransactionSet with a basis referencing that block, we'll attempt to use it.

0.16.1 (2025-06-14)

Fixes

• Added defer recover to prevent nodes from panicking due to uncaught bugs.
• Fixed a panic when attempting to update element proofs.
• Update core to v0.13.2

... (truncated)

Commits

• See full diff in compare view

Updates go.sia.tech/coreutils from 0.16.4 to 0.16.5

Release notes

Sourced from go.sia.tech/coreutils's releases.

0.16.5 (2025-07-07)

Features

• Remove RedistributeV1|2 in favour of Redistribute. Return the index so the caller can use it as the basis when broadcasting the transactions.

Fixes

• Remove faulty utxo release, it is redundant since we lock utxos as the final step.
• Use only confirmed UTXOs for contract formation and renewals.

Changelog

Sourced from go.sia.tech/coreutils's changelog.

0.16.5 (2025-07-07)

Features

• Remove RedistributeV1|2 in favour of Redistribute. Return the index so the caller can use it as the basis when broadcasting the transactions.

Fixes

• Remove faulty utxo release, it is redundant since we lock utxos as the final step.
• Use only confirmed UTXOs for contract formation and renewals.

0.16.4 (2025-07-01)

Fixes

• Fix incorrect ordering of contract expirations preventing a consensus resync from scratch

0.16.3 (2025-06-19)

Features

• Require peers to support V2.

Fixes

• Increase default MaxInflightRPCs
• prevent reverted coinbase transactions from spamming the transaction pool
• Update core to v0.14.0

0.16.2 (2025-06-17)

Fixes

• Fixed an issue with a single syncing peer from taking over the sync loop.

Don't ignore missing supplement in updateV2TransactionProofs

##265 by @​lukechampine

The logic introduced in #193 caused a panic when a block supplement was missing: we would create an empty supplement, try to use it, then panic with out-of-range when trying to fetch stuff from the empty supplement.

In case you're wondering how we could end up in a situation where we have a block, but not a supplement: the supplement is only calculated when we fully validate and apply the block. If we receive a block that isn't on the best chain, we'll store it without also computing and storing the supplement. If someone then calls V2TransactionSet with a basis referencing that block, we'll attempt to use it.

0.16.1 (2025-06-14)

Fixes

• Added defer recover to prevent nodes from panicking due to uncaught bugs.
• Fixed a panic when attempting to update element proofs.
• Update core to v0.13.2

... (truncated)

Commits

• See full diff in compare view

Updates go.sia.tech/coreutils from 0.16.4 to 0.16.5

Release notes

Sourced from go.sia.tech/coreutils's releases.

0.16.5 (2025-07-07)

Features

• Remove RedistributeV1|2 in favour of Redistribute. Return the index so the caller can use it as the basis when broadcasting the transactions.

Fixes

• Remove faulty utxo release, it is redundant since we lock utxos as the final step.
• Use only confirmed UTXOs for contract formation and renewals.

Changelog

Sourced from go.sia.tech/coreutils's changelog.

0.16.5 (2025-07-07)

Features

• Remove RedistributeV1|2 in favour of Redistribute. Return the index so the caller can use it as the basis when broadcasting the transactions.

Fixes

• Remove faulty utxo release, it is redundant since we lock utxos as the final step.
• Use only confirmed UTXOs for contract formation and renewals.

0.16.4 (2025-07-01)

Fixes

• Fix incorrect ordering of contract expirations preventing a consensus resync from scratch

0.16.3 (2025-06-19)

Features

• Require peers to support V2.

Fixes

• Increase default MaxInflightRPCs
• prevent reverted coinbase transactions from spamming the transaction pool
• Update core to v0.14.0

0.16.2 (2025-06-17)

Fixes

• Fixed an issue with a single syncing peer from taking over the sync loop.

Don't ignore missing supplement in updateV2TransactionProofs

##265 by @​lukechampine

The logic introduced in #193 caused a panic when a block supplement was missing: we would create an empty supplement, try to use it, then panic with out-of-range when trying to fetch stuff from the empty supplement.

In case you're wondering how we could end up in a situation where we have a block, but not a supplement: the supplement is only calculated when we fully validate and apply the block. If we receive a block that isn't on the best chain, we'll store it without also computing and storing the supplement. If someone then calls V2TransactionSet with a basis referencing that block, we'll attempt to use it.

0.16.1 (2025-06-14)

Fixes

• Added defer recover to prevent nodes from panicking due to uncaught bugs.
• Fixed a panic when attempting to update element proofs.
• Update core to v0.13.2

... (truncated)

Commits

• 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]

Superseded by #1180.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

4 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
explorer	⬜️ Ignored (Inspect)	Visit Preview		Jul 10, 2025 4:48pm
explorer-zen	⬜️ Ignored (Inspect)	Visit Preview		Jul 10, 2025 4:48pm
hostd	⬜️ Ignored (Inspect)	Visit Preview		Jul 10, 2025 4:48pm
renterd	⬜️ Ignored (Inspect)	Visit Preview		Jul 10, 2025 4:48pm

[changeset-bot]

⚠️ No Changeset found

Latest commit: ad5acf7

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR