chore: update deps

doc: update the release template for git flow changes

This will allow us to dedup contributors when generating release notes.

This will use either the mailmap file in the current repo, or the mailmap file
in the target repo, when generating the contributor stats.

Co-authored-by: Peter Rabbitson <ribasushi@protocol.ai>

Co-authored-by: Peter Rabbitson <ribasushi@protocol.ai>

mailmap support

Bumps [github.com/libp2p/go-libp2p-kad-dht](https://github.com/libp2p/go-libp2p-kad-dht) from 0.8.0 to 0.8.1.
- [Release notes](https://github.com/libp2p/go-libp2p-kad-dht/releases)
- [Commits](libp2p/go-libp2p-kad-dht@v0.8.0...v0.8.1)

Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

chore: update WebUI to 2.8.0

feat: webui v2.9.0

Update docs-beta links to final URLs

Change docs-beta link to its final path

…levra

docs: add pacman.store (@RubenKelevra) to the early testers

Updates docs link to non-beta site.

This isn't perfect (we only use sessions after resolving the root cid) but it's
better than what we have. The real solution is #7198 so we can use sessions
everywhere.

Bumps [github.com/stretchr/testify](https://github.com/stretchr/testify) from 1.5.1 to 1.6.0.
- [Release notes](https://github.com/stretchr/testify/releases)
- [Commits](stretchr/testify@v1.5.1...v1.6.0)

Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

…ibp2p/go-libp2p-kad-dht-0.8.1

chore(deps): bump github.com/libp2p/go-libp2p-kad-dht from 0.8.0 to 0.8.1

fix: update node to fix mocha tests

When publishing a value, flood. This ensures that our messages make it to the
network even if some of our peers are bad and/or overloaded.

Pubsub handles this internally now.

Consistently append `/p2p/QmMyId` to addresses when calling `ipfs id Me` and `ipfs id NotMe`.

Fixes #7378.

fix two pubsub issues.

This is a _protocol breaking_ change for the QUIC transport, the last one before
we stabilize it.

chore: update quic transport

Bumps [github.com/coreos/go-systemd/v22](https://github.com/coreos/go-systemd) from 22.0.0 to 22.1.0.
- [Release notes](https://github.com/coreos/go-systemd/releases)
- [Commits](coreos/go-systemd@v22.0.0...v22.1.0)

Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

…oreos/go-systemd/v22-22.1.0

chore(deps): bump github.com/coreos/go-systemd/v22 from 22.0.0 to 22.1.0

fix(commands): print consistent addresses in ipfs id

…tretchr/testify-1.6.0

chore(deps): bump github.com/stretchr/testify from 1.5.1 to 1.6.0

fix: use bitswap sessions for ipfs refs

due to major bugfixes in the .4 release

go: bump minimal dependency to 1.14.4

chore: add migration to listen on QUIC by default

1. Don't add quic addresses when they're already present (correctly detect quic addresses).
2. Correctly distinguish between quic addresses and quic + relay addresses.
3. Only add quic addresses to mirror tcp addresses, not tcp/ws addresses.

fixes #7444

fix(migration): correctly migrate quic addresses

readme: update go-version

1. We should have done this in 7-to-8 anyways, but didn't in some cases.
2. We assume these addresses use /p2p/ in the 9-to-10 migration.

fix(migration): migrate /ipfs/ bootstrappers to /p2p/

…ning

systemd: enable systemd hardening features

fix: Use the -p option in Dockerfile to make parents as needed

doc(config): expand peering docs

Hopefully, we can get the community to start pooling knowledge of how to run
go-ipfs in production.

Authors:
@lgierth @CameronNemo @jessicaschilling

URL: https://github.com/ipfs/website/blob/master/static/docs/examples/init/README.md

License: MIT

Readme: Update link about init systems (and import old readme)

doc(prod): start documenting production stuff

see #6402

systemd: specify repo path, to avoid unnecessary subdirectory

chore: bump webui version

This is more robust cross-platform/architecture.

fixes #7422

chore:bump webui version to 2.10.1

update QUIC

fix: use static binaries in docker container

chore: bump test dependencies

Simplify keeping the snap package up to date by including the snapcraft.yaml in the repo.

We can then wire up the snapstore to autobuild the package for amd64,i386,arm* etc.

Many thanks to @ElOpio for the work of getting ipfs into the snap store in the first place, and to @bertrandfalguiere and @mkg20001 for pushing it forwards.

See: https://github.com/ipfs-shipyard/ipfs-snap for more info.

Fixes #7250
WIP #3595

License: MIT
Signed-off-by: Oli Evans <oli@tableflip.io>

Without the home interface the user is unable to add files to ipfs from their home dir.

Also explicitly sets the build architectures, to skip some esoteric ones and save some cpu cycles.

License: MIT
Signed-off-by: Oli Evans <oli@tableflip.io>

remvoing as specifying the subset of architectures you want to build on has side-effects, like the resulting snap is labeled as "multi" arch, and the snapstore UI lists it as building on i386 the whole time.

License: MIT
Signed-off-by: Oli Evans <oli@tableflip.io>

This:

- adds subdomain gateway support for ED25519 CIDs in a way that fits in
  a single DNS label to enable TLS for every IPNS website.

- cleans up subdomain redirect logic and adds more explicit error
  handling.

TL;DR on router logic:

When CID is longer than 63 characters, router at /ipfs/* and /ipns/*
converts to Base36, and if that does not help, returns a human readable
400 Bad Request error.

Addressing code review:
#7441 (review)

refactor: use b36 for all libp2p-keys in subdomains
Consensus reached in
#7441 (comment)
#7441 (comment)
#7441 (comment)

* add flag to "ipfs key gen" to output keys in b36 CIDv1
* add flag to "ipfs key list" to output keys in b36 CIDv1
* add and modify corresponding sharness tests

* add support for choosing a peer key type (e.g. RSA or Ed25519) when initializing the repo
* test all variants of ipfs init: RSA, Ed25519 and default
* update subdomain gateway sharness test to publish IPNS using RSA and
Ed25519 keys
* use default identity bit lengths defined in config repo instead of
having separate defaults in go-ipfs
* update config repo dependency

Co-authored-by: Will Scott <will@cypherpunk.email>
Co-authored-by: Petar Maymounkov <petarm@gmail.com>

Choose Key type at initialization

…node