dependabot[bot] opened a new pull request, #58: URL: https://github.com/apache/incubator-milagro-dta/pull/58
Bumps [github.com/ipfs/go-ipfs](https://github.com/ipfs/go-ipfs) from 0.4.22 to 0.8.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/ipfs/go-ipfs/releases";>github.com/ipfs/go-ipfs's releases</a>.</em></p> <blockquote> <h2>v0.8.0</h2> <h1>go-ipfs 0.8.0 Release</h1> <p>We're happy to announce go-ipfs 0.8.0! This release is focused on making it easier to work with pins. We have some snazzy new features around being able to ask remote services to pin data for you, and modifying large pin sets is much faster than ever before.</p> <h2>๐ฆ Highlights</h2> <h3>๐งท Remote pinning services</h3> <p>There is now support for asking remote services to pin data for you.</p> <p>This comes with a redesign of how we're thinking about pinning and includes some commonly requested features such as:</p> <ul> <li>Pins can have names (and coming soon metadata)</li> <li>Data can be pinned in either the foreground or background</li> <li>Pins can be searched by name, CID, or status</li> </ul> <p>Command-line users benefit from <code>ipfs pin remote</code> commands, which simplify remote pinning operations. The built-in pinning service API client executes all the necessary remote calls under the hood. HTTP API users have access to new commands under <code>/api/v0/pin/remote</code>.</p> <p>As long a service supports the vendor-agnostic <a href="https://ipfs.github.io/pinning-services-api-spec/";>IPFS Pinning Service API</a>, it can be used directly in go-ipfs.</p> <p>Examples include:</p> <pre lang="sh"><code>ipfs pin remote service add mysrv https://my-service.example.com/api-endpoint myAccessToken ipfs pin remote service ls --stat # confirm service mysrv is available <p>ipfs pin remote add /ipfs/bafymydata --service=mysrv --name=myfile # will block until status is pinned ipfs pin remote ls --service=mysrv --name=myfile ipfs pin remote rm --serivce=mysrv --name=myfile</p> <p>ipfs pin remote add /ipfs/bafymydata2 --service=mysrv --name=myfile2 --background # queue pin request and finish instantly ipfs pin remote ls --service=mysrv --cid=bafymydata2 --status=queued,pinning,pinned,failed ipfs pin remote rm --serivce=mysrv --cid=bafymydata2 --status=queued,pinning,pinned,failed </code></pre></p> <p>More examples can be found under <code>ipfs pin remote --help</code></p> <p>A few notes:</p> <ul> <li>Remote pinning services work with recursive pins. This means commands like <code>ipfs pin remote ls</code> will not list indirectly pinned CIDs.</li> <li>By default, only finished, successful pins are listed. To list or remove pending/failed pins, pass explicit status: <code>--status=queued,pinning,pinned,failed</code></li> <li>While pinning service data is stored in the configuration file it cannot be edited directly via the <code>ipfs config</code> commands due to the sensitive nature of pinning service API keys. The <code>ipfs pin remote service</code> commands can be used for interacting with remote service settings.</li> <li>An OpenAPI <a href="https://github.com/ipfs/pinning-services-api-spec/blob/main/ipfs-pinning-service.yaml";>ipfs-pinning-service.yaml</a> makes it easy to create or <a href="https://github.com/ipfs/pinning-services-api-spec#code-generation";>generate</a> a compatible client/server. Anyone can implement it and allow for pin management.</li> </ul> <h3>๐ Remote MFS pinning policy</h3> <p>Every service added via <code>ipfs pin remote service add</code> can be tasked to update a pin every time MFS root changes:</p> <pre><code></tr></table> </code></pre> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/ipfs/go-ipfs/blob/master/CHANGELOG.md";>github.com/ipfs/go-ipfs's changelog</a>.</em></p> <blockquote> <h2>v0.8.0 2021-02-18</h2> <p>We're happy to announce go-ipfs 0.8.0! This is planned to be a fairly small release focused on integrating in the new pinning service/remote pinning <a href="https://github.com/ipfs/pinning-services-api-spec";>API</a> that makes the experience of managing pins across pinning services easier and more uniform.</p> <h3>๐ฆ Highlights</h3> <h4>๐งท Remote pinning services</h4> <p>There is now support for asking remote services to pin data for you. This means anyone can implement the <a href="https://ipfs.github.io/pinning-services-api-spec/";>spec</a> (developed in this <a href="https://github.com/ipfs/pinning-services-api-spec";>repo</a>) and allow for pin management.</p> <p>All of the CLI (and corresponding HTTP API) commands are available under <code>ipfs pin remote</code>.</p> <p>This remote pinning service comes with a redesign of how we're thinking about pinning and includes some commonly requested features such as:</p> <ul> <li>Pins can have names (and coming soon metadata)</li> <li>The same content can be pinned multiple times, but of course stored only once <ul> <li>This allows applications using the same pinning service to manage their own pins without worrying about removing content important to another application</li> </ul> </li> <li>Data can be pinned in either the foreground or background</li> </ul> <p>Examples include:</p> <pre><code>ipfs pin remote service add myservice https://myservice.tld:1234/api/path myaccess key <p>ipfs pin remote add /ipfs/bafymydata --service=myservice --name=myfile ipfs pin remote ls --service=myservice --name=myfile ipfs pin remote ls --service=myservice --cid=bafymydata ipfs pin remote rm --serivce=myservice --name=myfile </code></pre></p> <p>A few notes:</p> <p>Remote pinning services work with recursive pins. This means commands like <code>ipfs pin remote ls</code> will not list indirectly pinned CIDs.</p> <p>While pinning service data is stored in the configuration file it cannot be edited directly via the <code>ipfs config</code> commands due to the sensitive nature of pinning service API keys. The <code>ipfs pin remote service</code> commands can be used for interacting with remote service settings.</p> <h4>๐ Faster local pinning and unpinning</h4> <p>The pinning subsystem has been redesigned to be much faster and more flexible in how it tracks pins. For users who are working with many pins this will lead to a big speed increase in listing and modifying the set of pinned items as well as decreased memory usage.</p> <p>Part of the redesign was setup to account for being able to interact with local pins the same way we can now interact with remote pins (e.g. names, being allowed to pin the same CID multiple times, etc.). Keep posted for more improvements to pinning.</p> <h4>DNSLink names on https:// subdomains</h4> <p>Previously DNSLink names would have trouble loading over subdomain gateways with HTTPS support since there is no way to get multilevel wildcard certificates (e.g. <code>en.wikipedia-on-ipfs.org.ipns.dweb.link</code> cannot be covered by <code>*.ipns.dweb.link</code>). Therefore, when trying to load DNSLink names over https:// subdomains go-ipfs we now forward to an encoded DNS name. Since DNS names cannot contain <code>.</code> in them they are escaped using <code>-</code>.</p> <p><code>/ipns/en.wikipedia-on-ipfs.org</code> โ <code>ipns://en.wikipedia-on-ipfs.org</code> โ <code>https://dweb.link/ipns/en.wikipedia-on-ipfs.org</code> <code>https://en-wikipedia--on--ipfs-org.ipns.dweb.link</code> :point_left: <em>a single DNS label, no TLS error</em></p> <h4>QUIC update</h4> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/ipfs/go-ipfs/commit/ce693d7e81e0206b3afbce30333c21a36a9f094b";><code>ce693d7</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/ipfs/go-ipfs/issues/7924";>#7924</a> from ipfs/release-v0.8.0</li> <li><a href="https://github.com/ipfs/go-ipfs/commit/30fa364b516a7e333d21510eaa9446c740d7a21a";><code>30fa364</code></a> update CHANGELOG for v0.8.0</li> <li><a href="https://github.com/ipfs/go-ipfs/commit/9a20c9ebf22b08139f1a2bca8657bfddd3cd52c5";><code>9a20c9e</code></a> Release v0.8.0</li> <li><a href="https://github.com/ipfs/go-ipfs/commit/3d8321ab2e06b3705a497ad3f3168c24b5904c5f";><code>3d8321a</code></a> docs: RepinInterval</li> <li><a href="https://github.com/ipfs/go-ipfs/commit/94dd4be8f8fd074ca2a48734501b4b2332b629a9";><code>94dd4be</code></a> style: docs/config.md</li> <li><a href="https://github.com/ipfs/go-ipfs/commit/e29ae2e737a9f92f78ebb565457376b3712f40ca";><code>e29ae2e</code></a> style: improved MFS PinName example</li> <li><a href="https://github.com/ipfs/go-ipfs/commit/a40cbb03e1ae07d932b3dc93a5d274fb91458590";><code>a40cbb0</code></a> docs: Pinning.RemoteServices.Policies</li> <li><a href="https://github.com/ipfs/go-ipfs/commit/5e330b2806253961cb88d005fdc24e6d5c59e312";><code>5e330b2</code></a> Fix build issue with go1.16</li> <li><a href="https://github.com/ipfs/go-ipfs/commit/9b8308dc070d214e0d1bfbab1dfea5b61ec5ad67";><code>9b8308d</code></a> update deps</li> <li><a href="https://github.com/ipfs/go-ipfs/commit/4080333de16ff06eaa0c0d74e461e370a038ffcd";><code>4080333</code></a> Release v0.8.0-rc2</li> <li>Additional commits viewable in <a href="https://github.com/ipfs/go-ipfs/compare/v0.4.22...v0.8.0";>compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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 You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/apache/incubator-milagro-dta/network/alerts). </details> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
