chore(deps): bump the dependencies group across 1 directory with 2 updates

[dependabot]

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.21.6 to 0.21.7

Release notes

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

0.21.7 (2026-07-17)

Fixes

• Fix overflow bug in Currency.MulWithOverflow

Changelog

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

0.21.7 (2026-07-17)

Fixes

• Fix overflow bug in Currency.MulWithOverflow

Commits

• 5457cfa Merge pull request #422 from SiaFoundation/release
• 6d54395 chore: prepare release 0.21.7
• 78d08a7 build(deps): bump go.sia.tech/mux in the all-dependencies group
• ad557b1 types: fix overflow bug in Currency.MulWithOverflow
• fa431e0 build(deps): bump the all-dependencies group with 3 updates
• See full diff in compare view

Updates go.sia.tech/coreutils from 0.23.5 to 0.24.0

Release notes

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

0.24.0 (2026-08-04)

Breaking Changes

Support concurrent chain.Manager reads via MVCC snapshots

The Manager previously serialized all of its methods -- including read-only ones -- with a single mutex, so heavy read load (e.g. from the syncer or subscribers) contended with block processing. The Manager now follows an MVCC scheme: writes accumulate in the Store's "scratchpad" -- which includes the tip state -- and are committed by Flush, at which point they become visible to "snapshots": self-contained, read-only captures of the committed state. Read-only Manager methods operate on snapshots, so they proceed concurrently with each other and with block processing, and never stall writers. bbolt supports snapshots natively via read-only transactions; MemDB now implements them with pin-aware copy-on-flush generations (CacheDB delegates to its underlying DB).

This is a breaking change for implementors and consumers of the chain.DB and chain.Store interfaces:

• Store is now Snapshot() (StoreSnapshot, func()) + Scratchpad() StoreScratchpad. StoreSnapshot carries the read methods plus TipState; StoreScratchpad embeds it and adds the write methods and Flush, with ApplyBlock/RevertBlock updating the scratchpad's tip. Implementations may flush autonomously between operations (e.g. to bound the size or age of the accumulated writes), handling errors internally; the Manager explicitly calls Flush to publish the new tip after processing blocks, before notifying OnReorg listeners.
• DB mirrors Store: Snapshot() (DBSnapshot, release func()) + Scratchpad() DBScratchpad. The scratchpad carries Bucket/CreateBucket/Flush/Cancel and must not flush autonomously; snapshots are read-only and remain valid until released, even across concurrent Flushes. A single DBBucket interface serves both sides; its Put/Delete methods may return errors on read-only (snapshot) buckets.
• NewManager no longer takes a consensus.State parameter, and NewDBStore/NewDBStoreAtCheckpoint no longer return one; the tip state is provided by the Store itself (via a snapshot's or scratchpad's TipState).
• Reads reflect committed state. Pruned blocks remain visible to read-only methods until the next commit, and blocks added to non-best chains remain invisible to them until the next commit. Blocks that extend the best chain are always committed before AddBlocks returns and before OnReorg listeners fire, so subscribers observe the tip they are notified of.

Fixes

• reject nonunique txid txes from mempool
• Use max of chain height and price table height when storing sectors.

Changelog

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

0.24.0 (2026-08-04)

Breaking Changes

Support concurrent chain.Manager reads via MVCC snapshots

The Manager previously serialized all of its methods -- including read-only ones -- with a single mutex, so heavy read load (e.g. from the syncer or subscribers) contended with block processing. The Manager now follows an MVCC scheme: writes accumulate in the Store's "scratchpad" -- which includes the tip state -- and are committed by Flush, at which point they become visible to "snapshots": self-contained, read-only captures of the committed state. Read-only Manager methods operate on snapshots, so they proceed concurrently with each other and with block processing, and never stall writers. bbolt supports snapshots natively via read-only transactions; MemDB now implements them with pin-aware copy-on-flush generations (CacheDB delegates to its underlying DB).

This is a breaking change for implementors and consumers of the chain.DB and chain.Store interfaces:

• Store is now Snapshot() (StoreSnapshot, func()) + Scratchpad() StoreScratchpad. StoreSnapshot carries the read methods plus TipState; StoreScratchpad embeds it and adds the write methods and Flush, with ApplyBlock/RevertBlock updating the scratchpad's tip. Implementations may flush autonomously between operations (e.g. to bound the size or age of the accumulated writes), handling errors internally; the Manager explicitly calls Flush to publish the new tip after processing blocks, before notifying OnReorg listeners.
• DB mirrors Store: Snapshot() (DBSnapshot, release func()) + Scratchpad() DBScratchpad. The scratchpad carries Bucket/CreateBucket/Flush/Cancel and must not flush autonomously; snapshots are read-only and remain valid until released, even across concurrent Flushes. A single DBBucket interface serves both sides; its Put/Delete methods may return errors on read-only (snapshot) buckets.
• NewManager no longer takes a consensus.State parameter, and NewDBStore/NewDBStoreAtCheckpoint no longer return one; the tip state is provided by the Store itself (via a snapshot's or scratchpad's TipState).
• Reads reflect committed state. Pruned blocks remain visible to read-only methods until the next commit, and blocks added to non-best chains remain invisible to them until the next commit. Blocks that extend the best chain are always committed before AddBlocks returns and before OnReorg listeners fire, so subscribers observe the tip they are notified of.

Fixes

• reject nonunique txid txes from mempool
• Use max of chain height and price table height when storing sectors.

Commits

• cb3e753 Merge pull request #463 from SiaFoundation/release
• 12fe7cc chore: prepare release 0.24.0
• 4b4ff13 Merge pull request #450 from SiaFoundation/snapshot
• d53a68f bump webtransport-go
• ac51a5a build(deps): bump github.com/quic-go/quic-go from 0.60.0 to 0.61.0
• dd358f3 Merge origin/master into snapshot and resolve conflicts
• 5c25232 Merge pull request #462 from SiaFoundation/matt/reject-nonunique-txes
• 214c8cd Apply suggestions from code review
• 112b5ef address comments
• 30c80b9 chain: Fix MemDB Iter not observing unflushed writes
• Additional commits viewable in compare view

Updates go.sia.tech/core from 0.21.6 to 0.21.7

Release notes

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

0.21.7 (2026-07-17)

Fixes

• Fix overflow bug in Currency.MulWithOverflow

Changelog

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

0.21.7 (2026-07-17)

Fixes

• Fix overflow bug in Currency.MulWithOverflow

Commits

• 5457cfa Merge pull request #422 from SiaFoundation/release
• 6d54395 chore: prepare release 0.21.7
• 78d08a7 build(deps): bump go.sia.tech/mux in the all-dependencies group
• ad557b1 types: fix overflow bug in Currency.MulWithOverflow
• fa431e0 build(deps): bump the all-dependencies group with 3 updates
• See full diff in compare view

Updates go.sia.tech/coreutils from 0.23.5 to 0.24.0

Release notes

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

0.24.0 (2026-08-04)

Breaking Changes

Support concurrent chain.Manager reads via MVCC snapshots

The Manager previously serialized all of its methods -- including read-only ones -- with a single mutex, so heavy read load (e.g. from the syncer or subscribers) contended with block processing. The Manager now follows an MVCC scheme: writes accumulate in the Store's "scratchpad" -- which includes the tip state -- and are committed by Flush, at which point they become visible to "snapshots": self-contained, read-only captures of the committed state. Read-only Manager methods operate on snapshots, so they proceed concurrently with each other and with block processing, and never stall writers. bbolt supports snapshots natively via read-only transactions; MemDB now implements them with pin-aware copy-on-flush generations (CacheDB delegates to its underlying DB).

This is a breaking change for implementors and consumers of the chain.DB and chain.Store interfaces:

• Store is now Snapshot() (StoreSnapshot, func()) + Scratchpad() StoreScratchpad. StoreSnapshot carries the read methods plus TipState; StoreScratchpad embeds it and adds the write methods and Flush, with ApplyBlock/RevertBlock updating the scratchpad's tip. Implementations may flush autonomously between operations (e.g. to bound the size or age of the accumulated writes), handling errors internally; the Manager explicitly calls Flush to publish the new tip after processing blocks, before notifying OnReorg listeners.
• DB mirrors Store: Snapshot() (DBSnapshot, release func()) + Scratchpad() DBScratchpad. The scratchpad carries Bucket/CreateBucket/Flush/Cancel and must not flush autonomously; snapshots are read-only and remain valid until released, even across concurrent Flushes. A single DBBucket interface serves both sides; its Put/Delete methods may return errors on read-only (snapshot) buckets.
• NewManager no longer takes a consensus.State parameter, and NewDBStore/NewDBStoreAtCheckpoint no longer return one; the tip state is provided by the Store itself (via a snapshot's or scratchpad's TipState).
• Reads reflect committed state. Pruned blocks remain visible to read-only methods until the next commit, and blocks added to non-best chains remain invisible to them until the next commit. Blocks that extend the best chain are always committed before AddBlocks returns and before OnReorg listeners fire, so subscribers observe the tip they are notified of.

Fixes

• reject nonunique txid txes from mempool
• Use max of chain height and price table height when storing sectors.

Changelog

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

0.24.0 (2026-08-04)

Breaking Changes

Support concurrent chain.Manager reads via MVCC snapshots

The Manager previously serialized all of its methods -- including read-only ones -- with a single mutex, so heavy read load (e.g. from the syncer or subscribers) contended with block processing. The Manager now follows an MVCC scheme: writes accumulate in the Store's "scratchpad" -- which includes the tip state -- and are committed by Flush, at which point they become visible to "snapshots": self-contained, read-only captures of the committed state. Read-only Manager methods operate on snapshots, so they proceed concurrently with each other and with block processing, and never stall writers. bbolt supports snapshots natively via read-only transactions; MemDB now implements them with pin-aware copy-on-flush generations (CacheDB delegates to its underlying DB).

This is a breaking change for implementors and consumers of the chain.DB and chain.Store interfaces:

• Store is now Snapshot() (StoreSnapshot, func()) + Scratchpad() StoreScratchpad. StoreSnapshot carries the read methods plus TipState; StoreScratchpad embeds it and adds the write methods and Flush, with ApplyBlock/RevertBlock updating the scratchpad's tip. Implementations may flush autonomously between operations (e.g. to bound the size or age of the accumulated writes), handling errors internally; the Manager explicitly calls Flush to publish the new tip after processing blocks, before notifying OnReorg listeners.
• DB mirrors Store: Snapshot() (DBSnapshot, release func()) + Scratchpad() DBScratchpad. The scratchpad carries Bucket/CreateBucket/Flush/Cancel and must not flush autonomously; snapshots are read-only and remain valid until released, even across concurrent Flushes. A single DBBucket interface serves both sides; its Put/Delete methods may return errors on read-only (snapshot) buckets.
• NewManager no longer takes a consensus.State parameter, and NewDBStore/NewDBStoreAtCheckpoint no longer return one; the tip state is provided by the Store itself (via a snapshot's or scratchpad's TipState).
• Reads reflect committed state. Pruned blocks remain visible to read-only methods until the next commit, and blocks added to non-best chains remain invisible to them until the next commit. Blocks that extend the best chain are always committed before AddBlocks returns and before OnReorg listeners fire, so subscribers observe the tip they are notified of.

Fixes

• reject nonunique txid txes from mempool
• Use max of chain height and price table height when storing sectors.

Commits

• cb3e753 Merge pull request #463 from SiaFoundation/release
• 12fe7cc chore: prepare release 0.24.0
• 4b4ff13 Merge pull request #450 from SiaFoundation/snapshot
• d53a68f bump webtransport-go
• ac51a5a build(deps): bump github.com/quic-go/quic-go from 0.60.0 to 0.61.0
• dd358f3 Merge origin/master into snapshot and resolve conflicts
• 5c25232 Merge pull request #462 from SiaFoundation/matt/reject-nonunique-txes
• 214c8cd Apply suggestions from code review
• 112b5ef address comments
• 30c80b9 chain: Fix MemDB Iter not observing unflushed writes
• Additional commits viewable in compare view

[claude]

Claude Code Review

Claude Code Review is paused for this repository. To reconnect it, an admin of this repository's GitHub organization (or the account owner, for personal repositories) who can also manage your Claude organization's Code Review settings needs to re-link GitHub in Code Review settings. This is a one-time step.

_{Tip: disable this comment in your organization's Code Review settings.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

5 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
explorer	Ignored	Preview	Aug 21, 2026 9:33am
explorer-zen	Ignored	Preview	Aug 21, 2026 9:33am
hostd	Ignored	Preview	Aug 21, 2026 9:33am
indexd	Ignored	Preview	Aug 21, 2026 9:33am
renterd	Ignored	Preview	Aug 21, 2026 9:33am

[changeset-bot]

⚠️ No Changeset found

Latest commit: 0716fb8

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

[claude]

Claude Code Review

Claude Code Review is paused for this repository. To reconnect it, an admin of this repository's GitHub organization (or the account owner, for personal repositories) who can also manage your Claude organization's Code Review settings needs to re-link GitHub in Code Review settings. This is a one-time step.

_{Tip: disable this comment in your organization's Code Review settings.}