Skip to content
This repository has been archived by the owner on Jun 27, 2023. It is now read-only.

build(deps): bump github.com/ipfs/go-merkledag from 0.5.1 to 0.8.1 #132

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Dec 8, 2022

Bumps github.com/ipfs/go-merkledag from 0.5.1 to 0.8.1.

Release notes

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

v0.8.1

What's Changed

Full Changelog: ipfs/go-merkledag@v0.8.0...v0.8.1

v0.8.0

What's Changed

Breaking API changes in this release are the addition of error returns which should be checked:

  • (*ProtoNode).SetCidBuilder: changed from func(github.com/ipfs/go-cid.Builder) to func(github.com/ipfs/go-cid.Builder) error
  • (*ProtoNode).SetLinks: changed from func([]*github.com/ipfs/go-ipld-format.Link) to func([]*github.com/ipfs/go-ipld-format.Link) error

Additional errors may be returned on ProtoNode state change operations where those changes may put the ProtoNode instance into an unencodable state.

Full Changelog: ipfs/go-merkledag@v0.7.0...v0.8.0

v0.7.0

What's Changed

Full Changelog: ipfs/go-merkledag@v0.6.0...v0.7.0

v0.6.0

What's Changed

Full Changelog: ipfs/go-merkledag@v0.5.1...v0.6.0

Commits
  • 503ecaa chore: bump version to 0.8.1
  • 738cf43 feat: remove panic() from non-error methods
  • 51b4c32 feat: improve broken cid.Builder testing for CidBuilder
  • 0e4726d chore: bump version to 0.8.0
  • 62ec19c doc: document potential panics and how to avoid them
  • 3b5c1ef fix: simplify Cid generation cache & usage
  • 2a1cd35 feat: check links on setting and sanitise on encoding
  • bb220e8 feat: check that the CidBuilder hasher is usable
  • 8335efd chore: bump version to 0.7.0
  • 5d2c09d fix: remove use of ioutil
  • 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

You can disable automated security fix PRs for this repo from the Security Alerts page.

@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Dec 8, 2022
@welcome
Copy link

welcome bot commented Dec 8, 2022

Thank you for submitting this PR!
A maintainer will be here shortly to review it.
We are super grateful, but we are also overloaded! Help us by making sure that:

  • The context for this PR is clear, with relevant discussion, decisions
    and stakeholders linked/mentioned.

  • Your contribution itself is clear (code comments, self-review for the
    rest) and in its best form. Follow the code contribution
    guidelines

    if they apply.

Getting other community members to do a review would be great help too on complex PRs (you can ask in the chats/forums). If you are unsure about something, just leave us a comment.
Next steps:

  • A maintainer will triage and assign priority to this PR, commenting on
    any missing things and potentially assigning a reviewer for high
    priority items.

  • The PR gets reviews, discussed and approvals as needed.

  • The PR is merged by maintainers when it has been approved and comments addressed.

We currently aim to provide initial feedback/triaging within two business days. Please keep an eye on any labelling actions, as these will indicate priorities and status of your contribution.
We are very grateful for your contribution!

@dependabot dependabot bot force-pushed the dependabot/go_modules/github.com/ipfs/go-merkledag-0.8.1 branch from f3829e3 to 8191196 Compare January 12, 2023 10:46
Bumps [github.com/ipfs/go-merkledag](https://github.com/ipfs/go-merkledag) from 0.5.1 to 0.8.1.
- [Release notes](https://github.com/ipfs/go-merkledag/releases)
- [Commits](ipfs/go-merkledag@v0.5.1...v0.8.1)

---
updated-dependencies:
- dependency-name: github.com/ipfs/go-merkledag
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot force-pushed the dependabot/go_modules/github.com/ipfs/go-merkledag-0.8.1 branch from 8191196 to ec3c293 Compare February 9, 2023 19:02
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants