libp2p / go-libp2p-examples

Example libp2p applications
MIT License
339 stars 145 forks source link

Bump github.com/ipfs/go-datastore from 0.3.1 to 0.4.1 #114

Closed dependabot-preview[bot] closed 4 years ago

dependabot-preview[bot] commented 4 years ago

Bumps github.com/ipfs/go-datastore from 0.3.1 to 0.4.1.

Release notes

Sourced from github.com/ipfs/go-datastore's releases.

Release v0.4.1

Improve test suite so we can test flatfs.

Release v0.4.0

This is a major release only because it includes some breaking changes to previously unspecified behavior in the query logic to align it with expectations.

Prefixes

Prefixes in queries will now be cleaned (you may need to update your datastores for this).

Additionally, querying with a prefix /foo will now:

  • Match anything under /foo (including /foo/bar, etc.).
  • Not match /foo.
  • Not match /foobar.

This is what users want 90% of the time. Previously, one had to use the prefix /foo/ to mean "anything strictly under /foo. However, due to how key cleaning works, turning /foo/into a datastore key would result in/foo(which included/fooand/foobar`).

Mounts

Put: Given mounts at /foo and / in a mounted datastore, puts to /foo will now go in the / datastore, not /foo. Previously, puts to /foo would been written to / in the child datastore which isn't a valid key in many datastores.

Query: Previously, querying for the prefix /foo/ on a datastore with mounts /foo and / would search both datastores. However, keys starting with /foo living in / shouldn't be visible when another datastore is mounted at /foo.

Documentation

The behavior and edge cases of datastores is now better documented (and tested).

Commits
  • ac8b6e6 Merge pull request #148 from ipfs/test/capital
  • b026bf4 feat: add upper-case keys at a known prefix
  • b72ac7e Merge pull request #145 from ipfs/feat/enhance-tests
  • f2327ba test(suite): add a bunch of prefix tests for the new behavior
  • 83f9a95 Merge pull request #141 from ipfs/fix/ancestor-sep
  • 2fe8b68 test(query): be thurough
  • ae428d8 test: add a lookup test
  • bffc5fd doc(mount): fix and improve documentation
  • d009ffb doc: update and improve query docs
  • 5598edf fix(key): only count a key as an ancestor or prefix if there is a separator
  • Additional commits viewable in compare view


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)