Sourced from github.com/goccy/go-yaml's releases.

1.19.0

What's Changed

• Revert "feat: Dont make copies of structs for validation" by @​shuheiktgw in goccy/go-yaml#763
• Add decode option that allows specific field prefixes by @​cpuguy83 in goccy/go-yaml#795
• Normalize CR and CRLF in multi-line strings by @​shuheiktgw in goccy/go-yaml#754
• Support non string map keys by @​shuheiktgw in goccy/go-yaml#756
• Skip directive in path operations by @​shuheiktgw in goccy/go-yaml#758
• Add indentation to flow values on new lines by @​shuheiktgw in goccy/go-yaml#759
• Add support for RawMessage, similar to json.RawMessage by @​thanethomson in goccy/go-yaml#790

New Contributors

• @​cpuguy83 made their first contribution in goccy/go-yaml#795
• @​thanethomson made their first contribution in goccy/go-yaml#790

Full Changelog: https://github.com/goccy/go-yaml/compare/v1.18.0...v1.19.0

• a7b4bfb Add support for RawMessage, similar to json.RawMessage (#790)
• 07c09c0 Add indentation to flow values on new lines (#759)
• 0040ab4 Skip directive in path operations (#758)
• 7901e98 Support non string map keys (#756)
• f4d1347 Normalize CR and CRLF in multi-line strings (#754)
• 90e8525 Add decode option that allows specific field prefixes (#795)
• 25e5d90 Revert "feat: Dont make copies of structs for validation (#737)" (#763)
• See full diff in compare view

Sourced from github.com/libp2p/go-libp2p-kad-dht's releases.

v0.36.0

[!NOTE] This release was brought to you by the Shipyard team.

Overview

This release brings major improvements to the Sweep provider system: detailed runtime statistics, persistence of reprovide state across restarts, and better connection handling. These features ship to Kubo users in v0.39.

Highlights

Sweep provider statistics API

The SweepingProvider now exposes detailed runtime statistics through a new Stats() method, enabling monitoring tools to track provider health and throughput.

Available metrics include:

• Queue sizes and worker utilization
• Reprovide schedule and progress
• Network statistics (connected peers, regions)
• Operation rates and success counts

This powers the ipfs provide stat command in Kubo v0.39+. See #1144.

Reprovide cycle persistence and resume

The Sweep provider now persists its state to the datastore and automatically resumes after restarts:

• Persistent progress: The provider saves its position in the reprovide cycle. On restart, it continues from where it stopped instead of starting over.
• Catch-up reproviding: If the node was offline, all CIDs overdue for reprovide are immediately queued.
• Persistent provide queue: Pending provide operations survive restarts.

This fixes the long-standing issue where restarts would reset the reprovide cycle. See #1167, #1170, #1176, #1193.

Connectivity callbacks

Users can now register callbacks to be notified when the provider's connectivity status changes. This enables applications to track and react to connectivity state transitions. See #1194.

Connection protection during provides

New option to protect libp2p connections and keep addresses in the peerstore during provide operations. This prevents the connection manager from pruning connections that are actively being used for provides. See #1172.

Metric rename: provider_provides_total

The Sweep provider metric has been renamed from total_provide_count_total to provider_provides_total to follow OpenTelemetry naming conventions and match other kad-dht metrics.

Migration: Update any Prometheus queries or dashboards using the old metric name. See #1195.

... (truncated)

• f46f48a new version (#1204)
• 958a349 update dependencies (#1205)
• cf74329 chore(deps): bump golang.org/x/crypto from 0.42.0 to 0.45.0 (#1203)
• 6d2d861 fix(provider): protect SweepingProvider.wg (#1200)
• 7eb605c fix(ResettableKeystore): race when closing during reset (#1201)
• 58b46ba fix(provider): conflict resolution (#1199)
• 47e51c0 fix(provider): remove from trie by pruning prefix (#1198)
• 3fa0f96 fix(provider): rename metric to follow OpenTelemetry conventions (#1195)
• 1acbd9b fix(provider): resume cycle from persisted keystore (#1193)
• edead48 feat(provider): connectivity callbacks (#1194)
• Additional commits viewable in compare view

Sourced from github.com/ethereum/go-ethereum's releases.

Ballistic Drift Stabilizer (v1.16.7)

This is a re-roll of v1.16.6, including an important fix in the KZG cryptography library.

This release enables the Fusaka hardfork on Ethereum mainnet.

The Fusaka fork is scheduled to occur at 2025-12-03 21:49:11 UTC. Please upgrade your node to v1.16.7 in time for the fork.

This release also enables two blob-parameter-only (BPO) upgrades. These upgrades change protocol parameters to increase the available blob capacity.

• BPO1 on2025-12-09
• BPO2 on 2026-01-07

Fusaka

• Set mainnet timestamps for Osaka (#33063)
• Enable Fusaka for geth --dev mode (#32917)

RPC

• Add eth_sendRawTransactionSync which waits until either a timeout or the transaction is mined. This feature is mostly useful on L2s with lower blocktimes. (#32830, #32930, #32929)
• Add support for eth_simulateV1 in ethclient (#32856)
• Fix for an issue that might crash debug_traceCall (#33015)
• Fix for an issuer where local transactions were not persisted to the journal (#32921)

Core

• Fix for a cryptographic vulnerability in c-kzg-4844. This is only exploitable post-Fusaka. (#33093)
• Add geth --genesis flag as an alternative to running geth init genesis.json (#32844)
• Fix for receipt insertion during ERA file import. (#32934)
• Work on getting the trie node history in order to serve historical eth_getProof request with the new path-based archive node. (#32907, #32914, #32937)
• Further work on cmd/keeper, our guest program for zkVMs (#32816)
• Various optimizations (#32971, #32916, #32965, #32946)

Networking

• New metrics for tracking slow peers (#32964)
• Fix for an issue where disconnected peers were not removed in txFetcher (#32947)

---

For a full rundown of the changes please consult the Geth 1.16.6 and 1.16.7 release milestones.

As with all our previous releases, you can find the:

• Pre-built binaries for all platforms on our downloads page.
• Docker images published under ethereum/client-go (use "stable" tag).

... (truncated)

• b9f3a3d Merge branch 'master' into release/1.16
• 07129d2 version: release go-ethereum v1.16.7 stable
• 653f8d4 go.mod: update to c-kzg v2.1.5 (#33093)
• 5b77af3 version: begin v1.16.7 release cycle
• 386c3de Merge branch 'master' into release/1.16
• 044828e version: release go-ethereum v1.16.6
• 0250724 params: set osaka and BPO1 & BPO2 mainnet dates (#33063)
• 28c59b7 core/rawdb: fix db inspector by supporting trienode history (#33087)
• 18a9027 common: fix duration comparison in PrettyAge (#33064)
• e6d34c1 eth/tracers: fix prestateTracer for EIP-6780 SELFDESTRUCT (#33050)
• Additional commits viewable in compare view

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