build(deps): Bump github.com/lazyledger/nmt from 0.2.0 to 0.2.1 #214
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps [github.com/lazyledger/nmt](https://github.com/lazyledger/nmt) from 0.2.0 to 0.2.1. - [Release notes](https://github.com/lazyledger/nmt/releases) - [Commits](celestiaorg/nmt@v0.2.0...v0.2.1) Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
requested review from
evan-forbes,
liamsi and
tac0turtle
as code owners
|
Dependabot tried to add |
dependabot
bot
added
the
T:dependencies
|
Despite the new version number, this release is actually API-breaking. Hence, it requires manual work to update to this version. I'll close this in favor of a manual PR that also fixes the places where the type IntervalDigest is used. |
liamsi
deleted the
dependabot/go_modules/github.com/lazyledger/nmt-0.2.1
branch
|
@liamsi, I was going to update everything within DA consensus PR and actually did that already. If necessary, I can do that in the separate PR though or we can mention the DA PR also closes the issue you've just created. Also, should I retag |
Next time. No need to retag. I do not think it is currently used by any other project (so I wouldn't worry too much about semver semantics - we should start caring as soon as we tag a 1.0.0 release though) and there will be a 0.3.0 release soon anyway. I should document this in the repo (in contributing.md or sth like this).
Yeah, updating the nmt in that PR is OK, especially as you've done that already. In general, smaller, self-contained PRs are definitely preferred for many reasons. For instance reworking the inner/leaf nodes in the ipld plugin should be in a separate PR though. |
Bumps github.com/lazyledger/nmt from 0.2.0 to 0.2.1.
Release notes
Sourced from github.com/lazyledger/nmt's releases.
Commits
e0a317aMerge pull request #22 from lazyledger/hlib/digest-validationa5c8085remove panic from IntervalDigestFromBytesDependabot 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)