Skip to content

Releases: ipfs/kubo

v0.18.1

30 Jan 15:21
v0.18.1
675f8bd
Compare
Choose a tag to compare

πŸ”¦ Highlights

New default Pubsub.SeenMessagesStrategy

A new optional Pubsub.SeenMessagesStrategy configuration option has been added.

This option allows you to choose between two different strategies for
deduplicating messages: first-seen and last-seen.

When unset, the default strategy is last-seen, which calculates the
time-to-live (TTL) countdown based on the last time a message is seen. This
means that if a message is received and then seen again within the specified
TTL window based on the last time it was seen, it won't be emitted.

If you prefer the old behavior, which calculates the TTL countdown based on the
first time a message is seen, you can set Pubsub.SeenMessagesStrategy to
first-seen.

Improving libp2p resource management integration

This builds on the default protection nodes get against DoS (resource exhaustion) and eclipse attacks
with the go-libp2p Network Resource Manager/Accountant
that was fine-tuned in Kubo 0.18.

Adding default hard-limits from the Resource Manager/Accountant after the fact is tricky,
and some additional improvements have been made to improve the computed defaults.
As much as possible, the aim is for a user to only think about how much memory they want to bound libp2p to,
and not need to think about translating that to hard numbers for connections, streams, etc.
More updates are likely in future Kubo releases, but with this release:

  1. System.StreamsInbound is no longer bounded directly
  2. System.ConnsInbound, Transient.Memory, Transiet.ConnsInbound have higher default computed values.

Changelog

Full Changelog
  • github.com/ipfs/kubo:
    • Add overview section
    • Adjust inbound connection limits depending on memory.
    • feat: Pubsub.SeenMessagesStrategy (#9543) (ipfs/kubo#9543)
    • chore: update version
  • github.com/libp2p/go-libp2p-pubsub (v0.8.2 -> v0.8.3):

Contributors

Contributor Commits Lines Β± Files Changed
Mohsin Zaidi 2 +511/-55 12
Antonio Navarro Perez 2 +57/-57 5
galargh 1 +1/-1 1

v0.18.0

23 Jan 17:00
v0.18.0
6750377
Compare
Choose a tag to compare

πŸ”¦ Highlights

Content routing

Default InterPlanetary Network Indexer

Content routing is the process of discovering which peers provide a piece of content. Kubo has traditionally only supported libp2p's implementation of Kademlia DHT for content routing.

Kubo can now bridge networks by including support for the delegated routing HTTP API. Users can compose content routers using the Routing.Routers config to pick content routers with different tradeoffs than a Kademlia DHT (e.g., high-performance and high-capacity centralized endpoints, dedicated Kademlia DHT nodes, routers with unique provider records, privacy-focused content routers).

One example is InterPlanetary Network Indexers, which are HTTP endpoints that cache records from both the IPFS network and other sources such as web3.storage and Filecoin. This improves not only content availability by enabling Kubo to transparently fetch content directly from Filecoin storage providers, but also improves IPFS content routing latency by an order of magnitude and decreases resource consumption.

Note: it's possible to retrieve content stored by Filecoin Storage Providers (SPs) from Kubo if the SPs service Bitswap requests. As of this release, some SPs are advertising Bitswap. You can follow the roadmap progress for IPNIs and Bitswap in SPs here.

In this release, the default content router is changed from dht to auto. The auto router includes the IPFS DHT in addition to the cid.contact IPNI instance. In future releases, we plan to expand the functionality of auto to encompass automatic discovery of content routers, which will improve performance and content availability (for example, see IPIP-342).

Previous behavior can be restored by setting Routing.Type to dht.

Alternative routing rules, including alternative IPNI endpoints, can be configured in Routing.Routers after setting Routing.Type to custom.

Learn more in the Routing docs.

Increase provider record republish interval and expiration

Default Reprovider.Interval changed from 12h to 22h to match new defaults for the Provider Record Expiration (48h) in go-libp2p-kad-dht v0.20.0.

The rationale for increasing this can be found in
RFM 17: Provider Record Livenes Report,
kubo#9326,
and the upstream DHT specifications at libp2p/specs#451.

Learn more in the Reprovider config.

Gateways

(DAG-)JSON and (DAG-)CBOR response formats

The IPFS project has reserved the corresponding media types at IANA:

This release implements them as part of IPIP-328
and adds Gateway support for CIDs with json (0x0200), cbor (0x51),
dag-json (0x0129)
and dag-cbor (0x71) codecs.

To specify the response Content-Type explicitly, the HTTP client can override
the codec present in the CID by using the format parameter
or setting the Accept HTTP header:

  • Plain JSON: ?format=json or Accept: application/json
  • Plain CBOR: ?format=cbor or Accept: application/cbor
  • DAG-JSON: ?format=dag-json or Accept: application/vnd.ipld.dag-json
  • DAG-CBOR: ?format=dag-cbor or Accept: application/vnd.ipld.dag-cbor

In addition, when DAG-JSON or DAG-CBOR is requested with the Accept header
set to text/html, the Gateway will return a basic HTML page with download
options, improving the user experience in web browsers.

Example 1: DAG-CBOR and DAG-JSON Conversion on Gateway

The Gateway supports conversion between DAG-CBOR and DAG-JSON for efficient
end-to-end data structure management: author in CBOR or JSON, store as binary
CBOR and retrieve as JSON via HTTP:

$ echo '{"test": "json"}' | ipfs dag put # implicit --input-codec dag-json --store-codec dag-cbor
bafyreico7mjtqtqhvawro3yud5uqn6sc33nzqb7b5j2d7pdmzer5nab4t4

$ ipfs block get bafyreico7mjtqtqhvawro3yud5uqn6sc33nzqb7b5j2d7pdmzer5nab4t4 | xxd
00000000: a164 7465 7374 646a 736f 6e              .dtestdjson

$ ipfs dag get bafyreico7mjtqtqhvawro3yud5uqn6sc33nzqb7b5j2d7pdmzer5nab4t4 # implicit --output-codec dag-json
{"test":"json"}

$ curl "http://127.0.0.1:8080/ipfs/bafyreico7mjtqtqhvawro3yud5uqn6sc33nzqb7b5j2d7pdmzer5nab4t4?format=dag-json"
{"test":"json"}
Example 2: Traversing CBOR DAGs

Placing a CID in CBOR Tag 42 enables the
creation of arbitrary DAGs. The equivalent DAG-JSON notation for linking
to different blocks is represented by { "/": "cid" }.

The Gateway supports traversing these links, enabling access to data
referenced by structures other than regular UnixFS directories:

$ echo '{"test.jpg": {"/": "bafybeigdyrzt5sfp7udm7hu76uh7y26nf3efuylqabf3oclgtqy55fbzdi"}}' | ipfs dag put
bafyreihspwy3zlkzgphmec5d3xb5g5njrqwotd46lyubnelbzktnmsxkq4 # dag-cbor document linking to unixfs file

$ ipfs resolve /ipfs/bafyreihspwy3zlkzgphmec5d3xb5g5njrqwotd46lyubnelbzktnmsxkq4/test.jpg
/ipfs/bafybeigdyrzt5sfp7udm7hu76uh7y26nf3efuylqabf3oclgtqy55fbzdi

$ ipfs dag stat bafyreihspwy3zlkzgphmec5d3xb5g5njrqwotd46lyubnelbzktnmsxkq4
Size: 119827, NumBlocks: 2

$ curl "http://127.0.0.1:8080/ipfs/bafyreihspwy3zlkzgphmec5d3xb5g5njrqwotd46lyubnelbzktnmsxkq4/test.jpg" > test.jpg
Example 3: UnixFS directory listing as JSON

Finally, Gateway now supports the same logical format projection from
DAG-PB to DAG-JSON as the ipfs dag get command, enabling the retrieval of directory listings as JSON instead of HTML:

$ export DIR_CID=bafybeigccimv3zqm5g4jt363faybagywkvqbrismoquogimy7kvz2sj7sq
$ curl -H "Accept: application/vnd.ipld.dag-json" "http://127.0.0.1:8080/ipfs/$DIR_CID" | jq
$ curl "http://127.0.0.1:8080/ipfs/$DIR_CID?format=dag-json" | jq
{
  "Data": {
    "/": {
      "bytes": "CAE"
    }
  },
  "Links": [
    {
      "Hash": {
        "/": "Qmc3zqKcwzbbvw3MQm3hXdg8BQoFjGdZiGdAfXAyAGGdLi"
      },
      "Name": "1 - Barrel - Part 1 - alt.txt",
      "Tsize": 21
    },
    {
      "Hash": {
        "/": "QmdMxMx29KVYhHnaCc1icWYxQqXwUNCae6t1wS2NqruiHd"
      },
      "Name": "1 - Barrel - Part 1 - transcript.txt",
      "Tsize": 195
    },
    {
      "Hash": {
        "/": "QmawceGscqN4o8Y8Fv26UUmB454kn2bnkXV5tEQYc4jBd6"
      },
      "Name": "1 - Barrel - Part 1.png",
      "Tsize": 24862
    }
  ]
}
$ ipfs dag get $DIR_CID
{"Data":{"/":{"bytes":"CAE"}},"Links":[{"Hash":{"/":"Qmc3zqKcwzbbvw3MQm3hXdg8BQoFjGdZiGdAfXAyAGGdLi"},"Name":"1 - Barrel - Part 1 - alt.txt","Tsize":21},{"Hash":{"/":"QmdMxMx29KVYhHnaCc1icWYxQqXwUNCae6t1wS2NqruiHd"},"Name":"1 - Barrel - Part 1 - transcript.txt","Tsize":195},{"Hash":{"/":"QmawceGscqN4o8Y8Fv26UUmB454kn2bnkXV5tEQYc4jBd6"},"Name":"1 - Barrel - Part 1.png","Tsize":24862}]}
🐎 Fast directory listings with DAG sizes

Fast listings are now enabled for all UnixFS directories: big and small.
There is no linear slowdown caused by reading size metadata from child nodes,
and the size of DAG representing child items is always present.

As an example, the CID
bafybeiggvykl7skb2ndlmacg2k5modvudocffxjesexlod2pfvg5yhwrqm represents a UnixFS
directory with over 10k files. Listing big directories was fast
since Kubo 0.13, but in this release it will also include the size column.

QUIC and WebTransport

WebTransport enabled by default

WebTransport is a new libp2p transport that was introduced in v0.16 that is based on top of QUIC and HTTP3.

This allows browser-based nodes to contact Kub...

Read more

v0.18.0-rc2

04 Jan 11:44
v0.18.0-rc2
Compare
Choose a tag to compare
v0.18.0-rc2 Pre-release
Pre-release

See the related issue: #9417

And the draft changelog: docs/changelogs/v0.18.md

v0.18.0-rc1

13 Dec 20:55
v0.18.0-rc1
ae774a3
Compare
Choose a tag to compare
v0.18.0-rc1 Pre-release
Pre-release

See the related issue: #9417

And the draft changelog: docs/changelogs/v0.18.md

v0.17.0

22 Nov 16:07
v0.17.0
4485d6b
Compare
Choose a tag to compare

πŸ—£ Discuss

If you have comments, questions, or feedback on this release, please post here.

If you experienced any bugs with the release, please post an issue.

πŸ”¦ Highlights

libp2p resource management enabled by default

To help protect nodes from DoS (resource exhaustion) and eclipse attacks,
go-libp2p released a Network Resource Manager with a host of improvements throughout 2022.

Kubo first exposed this functionality in Kubo 0.13,
but it was disabled by default.

The resource manager is now enabled by default to protect nodes.
The defaults balance providing protection from various attacks while still enabling normal usecases to work as expected.

If you want to adjust the defaults, then you can:

  1. bound the amount of memory and file descriptors that libp2p will use with Swarm.ResourceMgr.MaxMemory
    and Swarm.ResourceMgr.MaxFileDescriptors and/or
  2. override any specific resource scopes/limits with Swarm.ResourceMgr.Limits

See Swarm.ResourceMgr for

  1. what limits are set by default,
  2. example override configuration,
  3. how to access prometheus metrics and view grafana dashboards of resource usage, and
  4. how to set explicit "allow lists" to protect against eclipse attacks.

Implicit connection manager limits

Starting with this release, ipfs init will no longer store the default
Connection Manager
limits in the user config under Swarm.ConnMgr.

Users are still free to use this setting to set custom values, but for most use
cases, the defaults provided with the latest Kubo release should be sufficient.

To remove any custom limits and switch to the implicit defaults managed by Kubo:

$ ipfs config --json Swarm.ConnMgr '{}'

We will be adjusting defaults in the future releases.

TAR Response Format on Gateways

Implemented IPIP-288 which adds
support for requesting deserialized UnixFS directory as a TAR stream.

HTTP clients can request TAR response by passing the ?format=tar URL
parameter, or setting Accept: application/x-tar HTTP header:

$ export DIR_CID=bafybeigccimv3zqm5g4jt363faybagywkvqbrismoquogimy7kvz2sj7sq
$ curl -H "Accept: application/x-tar" "http://127.0.0.1:8080/ipfs/$DIR_CID" > dir.tar
$ curl "http://127.0.0.1:8080/ipfs/$DIR_CID?format=tar" | tar xv
bafybeigccimv3zqm5g4jt363faybagywkvqbrismoquogimy7kvz2sj7sq
bafybeigccimv3zqm5g4jt363faybagywkvqbrismoquogimy7kvz2sj7sq/1 - Barrel - Part 1 - alt.txt
bafybeigccimv3zqm5g4jt363faybagywkvqbrismoquogimy7kvz2sj7sq/1 - Barrel - Part 1 - transcript.txt
bafybeigccimv3zqm5g4jt363faybagywkvqbrismoquogimy7kvz2sj7sq/1 - Barrel - Part 1.png

Dialling /wss peer behind a reverse proxy

This release resolves a regression introduced in Kubo 0.16, making it possible
again to connect to a peer over a WebSockets endpoint (/wss) that is
deployed behind a reverse proxy.

More details in go-libp2p release notes.

Changelog

Full Changelog
  • github.com/ipfs/kubo:
    • chore: bump version to v0.17.0 (ipfs/kubo#9427)
    • chore: bump version to v0.17.0-rc2 (ipfs/kubo#9414)
    • Doc improvements and changelog for resource manager (#9413) (ipfs/kubo#9413)
    • fix(docs): typo
    • docs: document /wss fixes in 0.17
    • refactor(config): remove Swarm.ConnMgr defaults
    • fix(config): skip nulls in ResourceMgr
    • Apply go fmt
    • Update core/node/libp2p/rcmgr_defaults.go
    • Remove limitation by HighWater param.
    • Fix RM errors when acceleratedDHT is active
    • docs: Deprecate Reframe on docs. (#9401) (ipfs/kubo#9401)
    • chore: bump version to v0.17.0-rc1 (ipfs/kubo#9394)
    • feat: Improve ResourceManager UX (#9338) (ipfs/kubo#9338)
    • feat: ipfs-webui 2.20.0
    • docs: note log tail is broken (#9383) (ipfs/kubo#9383)
    • feat(gateway): TAR response format (#9029) (ipfs/kubo#9029)
    • fix: error when using huge json limit file
    • chore: go-multicodec v0.7.0
    • fix: remove old unused buggy coredag code
    • feat: Add command line completion for fish
    • chore: delete snap configuration (ipfs/kubo#9352)
    • docs: update scoop package
    • docs: init release issue template improvement process v0.16.0 (ipfs/kubo#9283)
    • feat: add delegated routing metrics (#9354) (ipfs/kubo#9354)
    • chore: create v0.17.md changelog (ipfs/kubo#9353)
    • docs: pin remote arg
    • feat: webui@v2.19.0
    • test(car): export/import of (dag-)cbor/json codecs
    • add refs local alias repo ls (#9320) (ipfs/kubo#9320)
    • docs(cmds): Clarify block fetching of refs endpoint.
    • chore(cmds): dag import: use ipld legacy decode (ipfs/kubo#9219)
    • fix ipfs swarm peering crash in offline mode (#9261) (ipfs/kubo#9261)
    • feat: remove provider delay interval in bitswap (#9053) (ipfs/kubo#9053)
    • feat: --reset flag on swarm limit command (#9310) (ipfs/kubo#9310)
    • fix: add InlineDNSLink flag to PublicGateways config (#9328) (ipfs/kubo#9328)
    • docs: Fix typo and grammar in README
    • ci: add stylecheck to golangci-lint (#9334) (ipfs/kubo#9334)
    • Fix: swarm stats all command
    • Merge release v0.16.0 back into master (ipfs/kubo#9324)
    • fix: Set default Methods value to nil
    • docs: add WebTransport docs (ipfs/kubo#9314)
    • chore: bump version to 0.17.0-dev
  • github.com/ipfs/go-delegated-routing (v0.6.0 -> v0.7.0):
  • github.com/ipfs/go-ipfs-files (v0.1.1 -> v0.2.0):
  • github.com/ipfs/go-unixfs (v0.4.0 -> v0.4.1):
  • github.com/ipld/go-ipld-prime (v0.18.0 -> v0.19.0):
    • Prepare v0.19.0
    • fix: correct json codec links & bytes handling
    • test(basicnode): increase test coverage for int and map types (#454) (ipld/go-ipld-prime#454)
    • fix: remove reliance on ioutil
    • run gofmt -s
    • bump go.mod to Go 1.18 and run go fix
    • feat: add kinded union to gendemo
  • github.com/libp2p/go-libp2p (v0.23.2 -> v0.23.4):
  • github.com/libp2p/go-netroute (v0.2.0 -> v0.2.1):
  • github.com/marten-seemann/qpack (v0.2.1 -> v0.3.0):
    • update to Ginkgo v2 (#30) ...
Read more

v0.17.0-rc2

16 Nov 14:35
v0.17.0-rc2
7a7ba20
Compare
Choose a tag to compare
v0.17.0-rc2 Pre-release
Pre-release

See the related issue: #9319

And the draft changelog: docs/changelogs/v0.17.md

v0.17.0-rc1

10 Nov 22:43
v0.17.0-rc1
3d2a764
Compare
Choose a tag to compare
v0.17.0-rc1 Pre-release
Pre-release

See the related issue: #9319

And the draft changelog: docs/changelogs/v0.17.md

v0.16.0

04 Oct 11:34
v0.16.0
38117db
Compare
Choose a tag to compare

πŸ—£ Discuss

If you have comments, questions, or feedback on this release, please post here.

If you experienced any bugs with the release, please post an issue.

πŸ”¦ Highlights

πŸ›£οΈ More configurable delegated routing system

Since Kubo v0.14.0 Reframe protocol has been supported as a new routing system.

Now, we allow to configure several routers working together, so you can have several reframe and dht routers making queries. You can use the special parallel and sequential routers to fill your needs.

Example configuration usage using the Filecoin Network Indexer and the DHT, making first a query to the indexer, and timing out after 3 seconds.

$ ipfs config Routing.Type --json '"custom"'

$ ipfs config Routing.Routers.CidContact --json '{
  "Type": "reframe",
  "Parameters": {
    "Endpoint": "https://cid.contact/reframe"
  }
}'

$ ipfs config Routing.Routers.WanDHT --json '{
  "Type": "dht",
  "Parameters": {
    "Mode": "auto",
    "PublicIPNetwork": true,
    "AcceleratedDHTClient": false
  }
}'

$ ipfs config Routing.Routers.ParallelHelper --json '{
  "Type": "parallel",
  "Parameters": {
    "Routers": [
        {
        "RouterName" : "CidContact",
        "IgnoreErrors" : true,
        "Timeout": "3s"
        },
        {
        "RouterName" : "WanDHT",
        "IgnoreErrors" : false,
        "Timeout": "5m",
        "ExecuteAfter": "2s"
        }
    ]
  }
}'

$ ipfs config Routing.Methods --json '{
      "find-peers": {
        "RouterName": "ParallelHelper"
      },
      "find-providers": {
        "RouterName": "ParallelHelper"
      },
      "get-ipns": {
        "RouterName": "ParallelHelper"
      },
      "provide": {
        "RouterName": "WanDHT"
      },
      "put-ipns": {
        "RouterName": "ParallelHelper"
      }
    }'

🌍 WebTransport new experimental Transport

A new feature of go-libp2p is WebTransport.

For now it is disabled by default and considered experimental.
If you find issues running it please report them to us.

In the future Kubo will listen on WebTransport by default for anyone already listening on QUIC addresses.

WebTransport is a new transport protocol currently under development by the IETF and the W3C, and already implemented by Chrome.
Conceptually, it’s like WebSocket run over QUIC instead of TCP. Most importantly, it allows browsers to establish (secure!) connections to WebTransport servers without the need for CA-signed certificates,
thereby enabling any js-libp2p node running in a browser to connect to any kubo node, with zero manual configuration involved.

The previous alternative is websocket secure, which require installing a reverse proxy and TLS certificates manually.

How to enable WebTransport

Thoses steps are temporary and wont be needed once we make it enabled by default.

  1. Enable the WebTransport transport:
    ipfs config Swarm.Transports.Network.WebTransport --json true
  2. Add a listener address for WebTransport to your Addresses.Swarm key, for example:
    [
      "/ip4/0.0.0.0/tcp/4001",
      "/ip4/0.0.0.0/udp/4001/quic",
      "/ip4/0.0.0.0/udp/4002/quic/webtransport"
    ]
  3. Restart your daemon to apply the config changes.

πŸ—ƒοΈ Hardened IPNS record verification

Records that do not have a valid IPNS V2 signature, or exceed the max size
limit, will no longer pass verification, and will be ignored by Kubo when
resolving /ipns/{libp2p-key} content paths.

Kubo continues publishing backward-compatible V1+V2 records that can be
resolved by V1-only (go-ipfs <0.9.0) clients.

More details can be found in Backward Compatibility, Record Creation, and
Record Verification sections of the updated IPNS
specification
.

πŸŒ‰ Web Gateways now support _redirects files

This feature enables support for redirects, single-page applications (SPA),
custom 404 pages, and moving to IPFS-backed website hosting
without breaking existing HTTP links.

It is limited to websites hosted in web contexts with unique
Origins, such as
subdomain and
DNSLink gateways.
Redirect logic is evaluated only if the requested path is not in the DAG.

See more details and usage examples see
docs.ipfs.tech: Redirects, custom 404s, and SPA support.

😻 Add files to MFS with ipfs add --to-files

Users no longer need to call ipfs files cp after ipfs add to create a
reference in MFS, or deal with
low level pins if they do not wish to do so. It is now possible to pass MFS
path in an optional --to-files to add data directly to MFS, without creating
a low level pin.

Before (Kubo <0.16.0):

$ ipfs add cat.jpg
QmCID
$ ipfs files cp /ipfs/QmCID /mfs-cats/cat.jpg
$ ipfs pin rm QmCID # removing low level pin, since MFS is protecting from gc

Kubo 0.16.0 collapses the above steps into one:

$ ipfs add --pin=false cat.jpg --to-files /mfs-cats/

A recursive add to MFS works too (below line will create /lots-of-cats/ directory in MFS):

$ ipfs add -r ./lots-of-cats/ --to-files /

For more information, see ipfs add --help and ipfs files --help.

Changelog

Full Changelog
  • github.com/ipfs/kubo:
    • fix: Set default Methods value to nil
    • docs: document remaining 0.16.0 features
    • docs: add WebTransport docs (ipfs/kubo#9308)
    • chore: bump version to 0.16.0-rc1
    • fix: ensure hasher is registered when using a hashing function
    • feat: add webtransport as an optin transport (ipfs/kubo#9293)
    • feat(gateway): _redirects file support (#8890) (ipfs/kubo#8890)
    • docs: fix typo in changelog-v0.16.0.md
    • Readme: Rewrite introduction and featureset (#9211) (ipfs/kubo#9211)
    • feat: Delegated routing with custom configuration. (#9274) (ipfs/kubo#9274)
    • Add to ipfs id -h options (#9229) (ipfs/kubo#9229)
    • chore: bump go-libp2p v0.23.1 (ipfs/kubo#9285)
    • feat(cmds/add): --to-files option automates files cp (#8927) (ipfs/kubo#8927)
    • docs: fix broken ENS DoH example (#9281) (ipfs/kubo#9281)
    • (ipfs/kubo#9258)
    • (ipfs/kubo#9213)
    • docs: small typo in Dockerfile
    • feat: ipfs-webui v2.18.1
    • feat: ipfs-webui v2.18.0 (#9262) (ipfs/kubo#9262)
    • bump go-libp2p v0.22.0 & go1.18&go1.19 (ipfs/kubo#9244)
    • docs: change windows choco install command to point to go-ipfs
    • fix: pass the repo directory into the ignored_commit function
    • docs(cmds): daemon: update DHTClient description
    • fix(gw): send 200 for empty files
    • docs(readme): official vs unofficial packages
    • chore: remove Gateway.PathPrefixes
    • docs(readme): update Docker section
    • docs: fix markdown syntax typo in v0.15's changelog
    • chore: Release v0.15.0 (ipfs/kubo#9236)
    • chore: fix undiallable api and gateway files (ipfs/kubo#9233)
    • chore: Bump version to 0.16.0-dev
  • github.com/ipfs/go-bitswap (v0.9.0 -> v0.10.2):
    • chore: release v0.10.2
    • fix: create a copy of the protocol slice in network.processSettings
    • chore: release v0.10.1
    • fix: incorrect type in the WithTracer polyfill option
    • chore: fix incorrect log message when a bad option is passed
    • chore: release v0.10.0
    • chore: update go-libp2p v0.22.0
  • github.com/ipfs/go-cid (v0.2.0 -> v0.3.2):
    • chore: release v0.3.2
    • Revert "fix: bring back, but deprecate CodecToStr and Codecs"
    • chore: release v0.2.1
    • fix: bring back, but deprecate CodecToStr and Codecs
    • run gofmt -s
    • bump go.mod to Go 1.18 and run go fix
    • chore: release v0.3.0
    • fix: return nil Bytes() if the Cid in undef
    • Add MustParse (ipfs/go-cid#139)
  • github.com/ipfs/go-datastore (v0.5.1 -> v0.6.0)...
Read more

v0.16.0-rc1

26 Sep 13:35
v0.16.0-rc1
Compare
Choose a tag to compare
v0.16.0-rc1 Pre-release
Pre-release

See the related issue: #9237

Or the draft changelog: docs/changelogs/v0.16.md

v0.15.0

30 Aug 09:49
v0.15.0
3ae52a4
Compare
Choose a tag to compare

πŸ—£ Discuss

If you have comments, questions, or feedback on this release, please post here.

If you experienced any bugs with the release, please post an issue.

πŸ”¦ Highlights

This is a release mainly with bugfixing and library updates.
We are improving release speed and cadence trying to have a new release every 5 weeks.

#️⃣ Blake 3 support

You can now use blake3 as a valid hash function:

  • ipfs block put --mhtype=blake3
  • ipfs add --hash=blake3
    It uses a 32 bytes default size.
    And verify up to 128 bytes.
    Because blake3 is variable output hash function, you can use a different digest length, set mhlen: ipfs block put --mhtype=blake3 --mhlen=64, ipfs add doesn't have this option yet.

πŸ’‰ Fx Options plugin

This adds a plugin interface that lets the plugin modify the fx options that are passed to fx when the app is initialized.
This means plugins can inject their own implementations of Kubo interfaces.
This enables granular customization of Kubo behavior by plugins, such as:

  • Bitswap with custom filters (e.g. for CID blocking)
  • Custom interface implementations such as Pinner or DAGService
  • Dynamic configuration of libp2p ...

Here's an example plugin that overrides the default Pinner with a custom one:

func (p *PinnerPlugin) Options(info core.FXNodeInfo) ([]fx.Option, error) {
	pinner := mypinner.New()    
	return append(info.FXOptions, fx.Replace(fx.Annotate(pinner, fx.As(new(pin.Pinner))))), nil
}

Extra plugin info here.

πŸ“ $IPFS_PATH/gateway file

This adds a new file in the IPFS_PATH folder similar to $IPFS_PATH/api containing an address based on Addresses.Gateway configuration.

This file is in URL (RFC1738) format.

$ cat ~/.ipfs/gateway
http://127.0.0.1:8080

Changelog

Full Changelog
Read more