Release v2.15.0 · ipfs/ipfs-companion

✨ Features

Display release notes upon Companion update (#913)

Just in case you care 🙈 to read release notes on each update.
This release opens them in a new tab, but future ones will make it less disruptive.
If you don't want to be interrupted, Preferences screen has a toggle to turn it off:

Quick import via HTTP API works with big files

IPFS Companion finally switched to the latest ipfs-http-client and modern JS API.

This introduced fantastic performance optimizations for web browser runtimes, made by @Gozala and @achingbrain.
Imported files are no longer buffered in memory and one can import much bigger files (4GB+) than before .

Persistence for manual opt-ins and opt-outs per site (#929)

Preferences screen now has separate list for opt-outs and opt-ins:

A site is added/moved between lists when user toggles integrations via browser action menu:

Mechanics are simple: direct match (sub.example.com) overrides decision made for a parent domain (`example.com).

Improved "Cannot process IPFS request" page (#911)

Thanks to @jessicaschilling we now have a better explainer when CIDv0 URI gets force-lowercased in Firefox:

Chromium 86 safelisted ipfs:// and other dweb protocol handlers, we hope to see similarly improved experience in Chromium-based browsers in the future.

🛠 Fixes and Maintenance

fix: default to https when recovering .eth (#847)
feat(ci): move to github, work on windows (#928)
refactor: switch to modern async await JS APIs (#811)
- latest js-ipfs and js-ipfs-http-client
- Web UI no longer included in Chromium bundle
- Instead, correct CID is detected and prefetched via IPFS
- Much faster install via one-click-install in Brave
fix: regression in HTTP recovery of background tabs (#915) (thank you @quevas13!)
docs(README): update screenshots for new UI (#909)
i18n: sync locale