Skip to content

Releases: ipni/index-provider

v0.15.5

23 Aug 17:10
69eb980
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.15.4...v0.15.5

v0.15.4

09 Jul 09:52
c282b0a
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.15.3...v0.15.4

v0.15.3

22 May 03:34
1bceeae
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.15.2...v0.15.3

v0.15.2

07 May 16:57
502dd50
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.15.1...v0.15.2

v0.15.0

19 Feb 18:54
a8b0416
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.14.3...v0.15.0

v0.14.3

10 Jan 13:40
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.14.2...v0.14.3

What's Changed

Full Changelog: v0.14.2...v0.14.3

v0.14.2

11 Sep 16:26
21793e3
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.14.1...v0.14.2

v0.14.1

04 Sep 05:59
e310668
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.13.6...v0.14.1

v0.14.0

01 Sep 16:53
0ad48e9
Compare
Choose a tag to compare

What's Changed

This release allows all index-providers to use the latest ipnisync protocol over HTTP, libp2p, or both. Upgrading a provider to this version will switch to serving ipnisync without any additional configuration changes or changes to infrastructure.

For details on configuring the index-provider, see the Publisher Configuration document.

Upgrade Behavior

For providers serving over data-transfer/graphsync, they will switch to serving ipnisync over their existing libp2p servers. They will also stop serving the old 'head' protocol over libp2p, and switch to serving the new ipnisync head protocol. They will not automatically ipnisync over HTTP unless configured to do so.

For providers that are using plain HTTP, they will continue to serve over plain HTTP as the new ipnisync publisher supports that, using the existing configuration. They will not automatically serve ipnisync over libp2p unless configured to do so.

New Capabilities

  • Providers can be configured to serve ipnisync over HTTP, over libp2p, or over both HTTP and libp2p.
  • Providers can be configured to serve over the discontinued data-transfer/graphsync as a temporary backup.
  • Mirror can serve over both HTTP and libp2p. If m.httpListenAddr has a value, then the mirror will serve over HTTP on that address. If there is a libp2p Host, then the mirror will serve ipnisync over libp2p using that host.

PRs in this Release

  • Upgrade to latest release of boxo and go-car by @masih in #402
  • Move command-specific flags into command source file by @gammazero in #407
  • Enable ipnisync to be served over libp2p. by @gammazero in #400

Full Changelog: v0.13.6...v0.14.0

v0.13.6

01 Sep 00:22
ca2ca88
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.13.5...v0.13.6