Skip to content

chore(deps): bump the dependencies group across 2 directories with 2 updates #1181

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
wants to merge 1 commit into from
Closed

chore(deps): bump the dependencies group across 2 directories with 2 updates #1181

wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jul 11, 2025 •
edited
Loading

⚠️ Dependabot is rebasing this PR ⚠️

Rebasing might not happen immediately, so don't worry if this takes some time.

Note: if you make any changes to this PR yourself, they will take precedence over the rebase.

Bumps the dependencies group with 2 updates in the /internal/cluster directory: go.sia.tech/core and go.sia.tech/coreutils.
Bumps the dependencies group with 2 updates in the /sdk directory: go.sia.tech/core and go.sia.tech/coreutils.

Updates go.sia.tech/core from 0.14.1 to 0.14.2

Release notes

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

0.14.2 (2025-07-07)

Features

Add RPCSendHeaders

#330 by @​lukechampine

Also removes RPCSendBlocks and RPCSendBlk (made obsolete by RPCSendV2Blocks and RPCSendCheckpoint), as well as RPCRelayHeader and RPCSendTransactionSet (as no more v1 blocks or v1 transactions can be mined). I could maybe see an argument for keeping the latter two, if we wanted to run a v1 testnet, but... why would we want to run a v1 testnet?

consensus: Reject V1BlockSupplement after require height

#329 by @​lukechampine

This is somewhat redundant since the chain.DBStore always returns an empty supplement after the require height, but it doesn't hurt to enforce it in core.

Changelog

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

0.14.2 (2025-07-07)

Features

Add RPCSendHeaders

##330 by @​lukechampine

Also removes RPCSendBlocks and RPCSendBlk (made obsolete by RPCSendV2Blocks and RPCSendCheckpoint), as well as RPCRelayHeader and RPCSendTransactionSet (as no more v1 blocks or v1 transactions can be mined). I could maybe see an argument for keeping the latter two, if we wanted to run a v1 testnet, but... why would we want to run a v1 testnet?

consensus: Reject V1BlockSupplement after require height

##329 by @​lukechampine

This is somewhat redundant since the chain.DBStore always returns an empty supplement after the require height, but it doesn't hurt to enforce it in core.

Commits
  • b30ee36 Merge pull request #331 from SiaFoundation/release
  • 29e92c0 chore: prepare release 0.14.2
  • 4512a02 Merge pull request #329 from SiaFoundation/v2-supplement
  • 0e6c4f0 knope: Add changeset
  • 7306ed9 consensus: Reject V1BlockSupplement after require height
  • 73ec591 Merge pull request #330 from SiaFoundation/headers-rpc
  • 4785369 consensus: Export ValidateHeader; ApplyOrphan -> ApplyHeader
  • 89c7c97 Auto generate changeset
  • 26f807f gateway: Remove obsolete v1 RPCs
  • e6cd994 gateway: Add RPCSendHeaders
  • 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

Updates go.sia.tech/core from 0.14.1 to 0.14.2

Release notes

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

0.14.2 (2025-07-07)

Features

Add RPCSendHeaders

#330 by @​lukechampine

Also removes RPCSendBlocks and RPCSendBlk (made obsolete by RPCSendV2Blocks and RPCSendCheckpoint), as well as RPCRelayHeader and RPCSendTransactionSet (as no more v1 blocks or v1 transactions can be mined). I could maybe see an argument for keeping the latter two, if we wanted to run a v1 testnet, but... why would we want to run a v1 testnet?

consensus: Reject V1BlockSupplement after require height

#329 by @​lukechampine

This is somewhat redundant since the chain.DBStore always returns an empty supplement after the require height, but it doesn't hurt to enforce it in core.

Changelog

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

0.14.2 (2025-07-07)

Features

Add RPCSendHeaders

##330 by @​lukechampine

Also removes RPCSendBlocks and RPCSendBlk (made obsolete by RPCSendV2Blocks and RPCSendCheckpoint), as well as RPCRelayHeader and RPCSendTransactionSet (as no more v1 blocks or v1 transactions can be mined). I could maybe see an argument for keeping the latter two, if we wanted to run a v1 testnet, but... why would we want to run a v1 testnet?

consensus: Reject V1BlockSupplement after require height

##329 by @​lukechampine

This is somewhat redundant since the chain.DBStore always returns an empty supplement after the require height, but it doesn't hurt to enforce it in core.

Commits
  • b30ee36 Merge pull request #331 from SiaFoundation/release
  • 29e92c0 chore: prepare release 0.14.2
  • 4512a02 Merge pull request #329 from SiaFoundation/v2-supplement
  • 0e6c4f0 knope: Add changeset
  • 7306ed9 consensus: Reject V1BlockSupplement after require height
  • 73ec591 Merge pull request #330 from SiaFoundation/headers-rpc
  • 4785369 consensus: Export ValidateHeader; ApplyOrphan -> ApplyHeader
  • 89c7c97 Auto generate changeset
  • 26f807f gateway: Remove obsolete v1 RPCs
  • e6cd994 gateway: Add RPCSendHeaders
  • 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

Updates go.sia.tech/core from 0.14.1 to 0.14.2

Release notes

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

0.14.2 (2025-07-07)

Features

Add RPCSendHeaders

#330 by @​lukechampine

Also removes RPCSendBlocks and RPCSendBlk (made obsolete by RPCSendV2Blocks and RPCSendCheckpoint), as well as RPCRelayHeader and RPCSendTransactionSet (as no more v1 blocks or v1 transactions can be mined). I could maybe see an argument for keeping the latter two, if we wanted to run a v1 testnet, but... why would we want to run a v1 testnet?

consensus: Reject V1BlockSupplement after require height

#329 by @​lukechampine

This is somewhat redundant since the chain.DBStore always returns an empty supplement after the require height, but it doesn't hurt to enforce it in core.

Changelog

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

0.14.2 (2025-07-07)

Features

Add RPCSendHeaders

##330 by @​lukechampine

Also removes RPCSendBlocks and RPCSendBlk (made obsolete by RPCSendV2Blocks and RPCSendCheckpoint), as well as RPCRelayHeader and RPCSendTransactionSet (as no more v1 blocks or v1 transactions can be mined). I could maybe see an argument for keeping the latter two, if we wanted to run a v1 testnet, but... why would we want to run a v1 testnet?

consensus: Reject V1BlockSupplement after require height

##329 by @​lukechampine

This is somewhat redundant since the chain.DBStore always returns an empty supplement after the require height, but it doesn't hurt to enforce it in core.

Commits
  • b30ee36 Merge pull request #331 from SiaFoundation/release
  • 29e92c0 chore: prepare release 0.14.2
  • 4512a02 Merge pull request #329 from SiaFoundation/v2-supplement
  • 0e6c4f0 knope: Add changeset
  • 7306ed9 consensus: Reject V1BlockSupplement after require height
  • 73ec591 Merge pull request #330 from SiaFoundation/headers-rpc
  • 4785369 consensus: Export ValidateHeader; ApplyOrphan -> ApplyHeader
  • 89c7c97 Auto generate changeset
  • 26f807f gateway: Remove obsolete v1 RPCs
  • e6cd994 gateway: Add RPCSendHeaders
  • 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

Updates go.sia.tech/core from 0.14.1 to 0.14.2

Release notes

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

0.14.2 (2025-07-07)

Features

Add RPCSendHeaders

#330 by @​lukechampine

Also removes RPCSendBlocks and RPCSendBlk (made obsolete by RPCSendV2Blocks and RPCSendCheckpoint), as well as RPCRelayHeader and RPCSendTransactionSet (as no more v1 blocks or v1 transactions can be mined). I could maybe see an argument for keeping the latter two, if we wanted to run a v1 testnet, but... why would we want to run a v1 testnet?

consensus: Reject V1BlockSupplement after require height

#329 by @​lukechampine

This is somewhat redundant since the chain.DBStore always returns an empty supplement after the require height, but it doesn't hurt to enforce it in core.

Changelog

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

0.14.2 (2025-07-07)

Features

Add RPCSendHeaders

##330 by @​lukechampine

Also removes RPCSendBlocks and RPCSendBlk (made obsolete by RPCSendV2Blocks and RPCSendCheckpoint), as well as RPCRelayHeader and RPCSendTransactionSet (as no more v1 blocks or v1 transactions can be mined). I could maybe see an argument for keeping the latter two, if we wanted to run a v1 testnet, but... why would we want to run a v1 testnet?

consensus: Reject V1BlockSupplement after require height

##329 by @​lukechampine

This is somewhat redundant since the chain.DBStore always returns an empty supplement after the require height, but it doesn't hurt to enforce it in core.

Commits
  • b30ee36 Merge pull request #331 from SiaFoundation/release
  • 29e92c0 chore: prepare release 0.14.2
  • 4512a02 Merge pull request #329 from SiaFoundation/v2-supplement
  • 0e6c4f0 knope: Add changeset
  • 7306ed9 consensus: Reject V1BlockSupplement after require height
  • 73ec591 Merge pull request #330 from SiaFoundation/headers-rpc
  • 4785369 consensus: Export ValidateHeader; ApplyOrphan -> ApplyHeader
  • 89c7c97 Auto generate changeset
  • 26f807f gateway: Remove obsolete v1 RPCs
  • e6cd994 gateway: Add RPCSendHeaders
  • 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

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 dependabot bot added dependencies Pull requests that update a dependency file go Pull requests that update Go code labels Jul 11, 2025
@vercel Vercel
Copy link

vercel bot commented Jul 11, 2025 •
edited
Loading

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 17, 2025 9:53am
explorer-zen ⬜️ Ignored (Inspect) Visit Preview Jul 17, 2025 9:53am
hostd ⬜️ Ignored (Inspect) Visit Preview Jul 17, 2025 9:53am
renterd ⬜️ Ignored (Inspect) Visit Preview Jul 17, 2025 9:53am

@changeset-bot changeset-bot
Copy link

changeset-bot bot commented Jul 11, 2025 •
edited
Loading

⚠️ No Changeset found

Latest commit: 8f9ed34

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.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

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

@dependabot dependabot bot force-pushed the dependabot/go_modules/internal/cluster/dependencies-77a4994b57 branch 2 times, most recently from fb96042 to e169825 Compare July 15, 2025 09:22
@dependabot
chore(deps): bump the dependencies group across 2 directories with 2 …
8f9ed34 
…updates

Bumps the dependencies group with 2 updates in the /internal/cluster directory: [go.sia.tech/core](https://github.com/SiaFoundation/core) and [go.sia.tech/coreutils](https://github.com/SiaFoundation/coreutils).
Bumps the dependencies group with 2 updates in the /sdk directory: [go.sia.tech/core](https://github.com/SiaFoundation/core) and [go.sia.tech/coreutils](https://github.com/SiaFoundation/coreutils).


Updates `go.sia.tech/core` from 0.14.1 to 0.14.2
- [Release notes](https://github.com/SiaFoundation/core/releases)
- [Changelog](https://github.com/SiaFoundation/core/blob/master/CHANGELOG.md)
- [Commits](SiaFoundation/core@v0.14.1...v0.14.2)

Updates `go.sia.tech/coreutils` from 0.16.5-0.20250701190511-6ece69f09f12 to 0.16.5
- [Release notes](https://github.com/SiaFoundation/coreutils/releases)
- [Changelog](https://github.com/SiaFoundation/coreutils/blob/master/CHANGELOG.md)
- [Commits](https://github.com/SiaFoundation/coreutils/commits/v0.16.5)

Updates `go.sia.tech/core` from 0.14.1 to 0.14.2
- [Release notes](https://github.com/SiaFoundation/core/releases)
- [Changelog](https://github.com/SiaFoundation/core/blob/master/CHANGELOG.md)
- [Commits](SiaFoundation/core@v0.14.1...v0.14.2)

Updates `go.sia.tech/coreutils` from 0.16.5-0.20250701190511-6ece69f09f12 to 0.16.5
- [Release notes](https://github.com/SiaFoundation/coreutils/releases)
- [Changelog](https://github.com/SiaFoundation/coreutils/blob/master/CHANGELOG.md)
- [Commits](https://github.com/SiaFoundation/coreutils/commits/v0.16.5)

Updates `go.sia.tech/core` from 0.14.1 to 0.14.2
- [Release notes](https://github.com/SiaFoundation/core/releases)
- [Changelog](https://github.com/SiaFoundation/core/blob/master/CHANGELOG.md)
- [Commits](SiaFoundation/core@v0.14.1...v0.14.2)

Updates `go.sia.tech/coreutils` from 0.16.4 to 0.16.5
- [Release notes](https://github.com/SiaFoundation/coreutils/releases)
- [Changelog](https://github.com/SiaFoundation/coreutils/blob/master/CHANGELOG.md)
- [Commits](https://github.com/SiaFoundation/coreutils/commits/v0.16.5)

Updates `go.sia.tech/core` from 0.14.1 to 0.14.2
- [Release notes](https://github.com/SiaFoundation/core/releases)
- [Changelog](https://github.com/SiaFoundation/core/blob/master/CHANGELOG.md)
- [Commits](SiaFoundation/core@v0.14.1...v0.14.2)

Updates `go.sia.tech/coreutils` from 0.16.4 to 0.16.5
- [Release notes](https://github.com/SiaFoundation/coreutils/releases)
- [Changelog](https://github.com/SiaFoundation/coreutils/blob/master/CHANGELOG.md)
- [Commits](https://github.com/SiaFoundation/coreutils/commits/v0.16.5)

---
updated-dependencies:
- dependency-name: go.sia.tech/core
  dependency-version: 0.14.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: go.sia.tech/coreutils
  dependency-version: 0.16.5
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: go.sia.tech/core
  dependency-version: 0.14.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: go.sia.tech/coreutils
  dependency-version: 0.16.5
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: go.sia.tech/core
  dependency-version: 0.14.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: go.sia.tech/coreutils
  dependency-version: 0.16.5
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: go.sia.tech/core
  dependency-version: 0.14.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dependencies
- dependency-name: go.sia.tech/coreutils
  dependency-version: 0.16.5
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: dependencies
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot force-pushed the dependabot/go_modules/internal/cluster/dependencies-77a4994b57 branch from e169825 to 8f9ed34 Compare July 17, 2025 09:52
@alexfreska alexfreska closed this Jul 18, 2025
@dependabot Dependabot
Copy link
Contributor Author

dependabot bot commented on behalf of github Jul 18, 2025

This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests.

To ignore these dependencies, configure ignore rules in dependabot.yml

@dependabot dependabot bot deleted the dependabot/go_modules/internal/cluster/dependencies-77a4994b57 branch July 18, 2025 12:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
dependencies Pull requests that update a dependency file go Pull requests that update Go code
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@alexfreska