libp2p / go-libp2p-examples

Example libp2p applications
MIT License
339 stars 145 forks source link

Bump github.com/libp2p/go-libp2p-core from 0.2.5 to 0.3.0 #104

Closed dependabot-preview[bot] closed 4 years ago

dependabot-preview[bot] commented 4 years ago

Bumps github.com/libp2p/go-libp2p-core from 0.2.5 to 0.3.0.

Release notes *Sourced from [github.com/libp2p/go-libp2p-core's releases](https://github.com/libp2p/go-libp2p-core/releases).* > ## v0.3.0 > ## PeerIDs encoded as CIDs > > In order to bring multibase support to peer IDs, we're slowly switching to encoding peer IDs as libp2p-key CIDs when formatted in text. They're currently formatted as raw base58 encoded multihashes. > > This release: > > * Adds support for encoding peer IDs as libp2p key CIDs (not used by default). > * Adds support for decoding libp2p key CIDs as peer IDs (enabled by default). > > ## Go 1.13 > > This release depends on go 1.13 as it uses go's built-in ed25519 library. If you are unable to upgrade, please work with the go team to address your issues with 1.13 and/or hold off on upgrading this package. > > ## P2P Multiaddrs > > We've switched the default libp2p multiaddr format from `/ipfs/Qm...` to `/p2p/Qm...` (in text only). All libp2p implementations have supported parsing these addresses for quite a while now so we don't expect any issues. > > See https://discuss.libp2p.io/t/multiaddr-format-change-ipfs-p2p/330. > > ## Bug Fixes > > As this is a release of the core package, there aren't all that many bug fixes. However: > > * We've fixed an issue in our metrics library that would cause it to report nonsensical bandwidth spikes in some cases (https://github-redirect.dependabot.com/libp2p/go-libp2p-core/issues/65) > * We've regenerated our protobufs to fix some potential parsing issues. > * We've fixed some potential multiaddr parsing issues.
Commits - [`f7f7248`](https://github.com/libp2p/go-libp2p-core/commit/f7f724862d85ec9f9ee7c58b0f79836abdee8cd9) Merge pull request [#98](https://github-redirect.dependabot.com/libp2p/go-libp2p-core/issues/98) from libp2p/dependabot/go_modules/github.com/multiform... - [`ee9d9da`](https://github.com/libp2p/go-libp2p-core/commit/ee9d9da3cfa8357c49b09e85ff24a511c6deb0fc) build(deps): bump github.com/multiformats/go-multiaddr - [`ba9101b`](https://github.com/libp2p/go-libp2p-core/commit/ba9101b58934544e0faa255cf826e2010d8a0973) feat: support encoding/decoding peer IDs as CIDs in text ([#41](https://github-redirect.dependabot.com/libp2p/go-libp2p-core/issues/41)) - [`4184c18`](https://github.com/libp2p/go-libp2p-core/commit/4184c18976c06ae114a6f3472ccc790213cf01be) Merge branch 'master' into feat/parse-cid-as-pid - [`edd5242`](https://github.com/libp2p/go-libp2p-core/commit/edd5242a11e1ad3165b7d0c4976f4a6643bcf4bb) Merge pull request [#95](https://github-redirect.dependabot.com/libp2p/go-libp2p-core/issues/95) from libp2p/chore/update-rest - [`af4f53a`](https://github.com/libp2p/go-libp2p-core/commit/af4f53a061ff02e8292a625307ba8e270eb1e66c) chore(dep): update btc (sekp) and openssl libraries - [`c4d6359`](https://github.com/libp2p/go-libp2p-core/commit/c4d6359d1617b7e08f0daff09953507be3b512f2) Merge pull request [#96](https://github-redirect.dependabot.com/libp2p/go-libp2p-core/issues/96) from libp2p/dependabot/go_modules/github.com/libp2p/go... - [`a986079`](https://github.com/libp2p/go-libp2p-core/commit/a986079787d5a52e569411e8bbf2c7ae9b58b0d0) build(deps): bump github.com/libp2p/go-openssl from 0.0.3 to 0.0.4 - [`f93c24d`](https://github.com/libp2p/go-libp2p-core/commit/f93c24de5d1fa7c1dbc8e25d0a3485436746d6d2) Merge pull request [#94](https://github-redirect.dependabot.com/libp2p/go-libp2p-core/issues/94) from libp2p/feat/std-ed25519 - [`d25b480`](https://github.com/libp2p/go-libp2p-core/commit/d25b4807f34ba1963338366a1c5a6125733f3b0d) docs(readme): specify minimum go version - Additional commits viewable in [compare view](https://github.com/libp2p/go-libp2p-core/compare/v0.2.5...v0.3.0)


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired)