opensource/kubo
1
0
Fork 0
mirror of https://github.com/ipfs/kubo.git synced 2025-05-17 06:57:40 +08:00
Code Issues Projects Releases Wiki Activity
Files
kubo/docs/changelogs/v0.34.md
Guillaume Michel 8af7f131e7 Update docs/changelogs/v0.34.md 
(cherry picked from commit 9de938479cca7c223bf87cba17b54ce59245e207)
2025-03-14 18:20:14 +01:00

6.8 KiB
Raw Blame History

Kubo changelog v0.34

v0.34.0

Overview

🔦 Highlights

AutoTLS now enabled by default for nodes with 1 hour uptime

Starting now, any publicly dialable Kubo node with a /tcp listener that remains online for at least one hour will receive a TLS certificate through the AutoTLS feature. This occurs automatically, with no need for manual setup.

To bypass the 1-hour delay and enable AutoTLS immediately, users can explicitly opt-in by running the following commands:

$ ipfs config --json AutoTLS.Enabled true
$ ipfs config --json AutoTLS.RegistrationDelay 0

AutoTLS will remain disabled under the following conditions:

  • The node already has a manually configured /ws (WebSocket) listener
  • A private network is in use with a swarm.key
  • TCP or WebSocket transports are disabled, or there is no /tcp listener

To troubleshoot, use GOLOG_LOG_LEVEL="error,autotls=info.

For more details, check out the AutoTLS configuration documentation or dive deeper with AutoTLS libp2p blog post.

RPC and CLI command changes

  • ipfs config is now validating json fields (#10679).
  • Deprecated the bitswap reprovide command. Make sure to switch to modern routing reprovide. (#10677)
  • The stats reprovide command now shows additional stats for Routing.AcceleratedDHTClient, indicating the last and next reprovide times. (#10677)
  • ipfs files cp now performs basic codec check and will error when source is not a valid UnixFS (only dag-pb and raw codecs are allowed in MFS)

Bitswap improvements from Boxo

This release includes performance and reliability improvements and fixes for minor resource leaks. One of the performance changes greatly improves the bitswap clients ability to operate under high load, that could previously result in an out of memory condition.

IPFS_LOG_LEVEL deprecated

The variable has been deprecated. Please use GOLOG_LOG_LEVEL instead for configuring logging levels.

Pebble datastore format update

If the pebble database format is not explicitly set in the config, then automatically upgrade it to the latest format version supported by the release ob pebble used by kubo. This will ensure that the database format is sufficiently up-to-date to be compatible with a major version upgrade of pebble. This is necessary before upgrading to use pebble v2.

Badger datastore update

An update was made to the badger v1 datastore that avoids use of mmap in 32-bit environments, which has been seen to cause issues on some platforms. Please be aware that this could lead to a performance regression for users of badger in a 32-bit environment. Badger users are advised to move to the flatds or pebble datastore.

Datastore Implementation Updates

The go-ds-xxx datastore implementations have been updated to support the updated go-datastore v0.8.2 query API. This update removes the datastore implementations' dependency on goprocess and updates the query API.

One Multi-error Package

Kubo previously depended on multiple multi-error packages, github.com/hashicorp/go-multierror and go.uber.org/multierr. These have nearly identical functionality so there was no need to use both. Therefore, go.uber.org/multierr was selected as the package to depend on. Any future code needing multi-error functionality should use go.uber.org/multierr to avoid introducing unneeded dependencies.

Fix hanging pinset operations during reprovides

The reprovide process can be quite slow. In default settings, the reprovide process will start reading CIDs that belong to the pinset. During this operation, starvation can occur for other operations that need pinset access (see https://github.com/ipfs/kubo/issue/10596). We have now switch to buffering pinset-related cids that are going to be reprovided in memory, so that we can free pinset mutexes as soon as possible so that pinset-writes and subsequent read operations can proceed. The downside is larger pinsets will need some extra memory, with an estimation of ~1GiB of RAM memory-use per 20 million items to be reprovided.

📦️ Important dependency updates

👨‍👩‍👧‍👦 Contributors