Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update rust crate sparse-merkle-tree to 0.6.0 #59

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 27, 2022

This PR contains the following updates:

Package Type Update Change
sparse-merkle-tree dependencies minor 0.5.3 -> 0.6.0

Release Notes

nervosnetwork/sparse-merkle-tree (sparse-merkle-tree)

v0.6.1

Compare Source

This release is a major update to the previous version. It includes a storage optimization: a new feature flag trie allows users to store the branch data in an optimized way, this feature flag is disabled by default for compatibility with the previous version.

Comparing to the previous version, the trie feature can reduce the storage usage by 90% and improve the performance by 15x (see benchmark). Users need to migrate the storage data from the previous version to the new version if they want to enable the trie feature flag, the migration process is simply creating the smt tree and inserting all the leaves from the previous data.

Changes
  • feat: load root from store #​32
  • feat: TrieTree implementation #​34

v0.6.0

Compare Source

v0.5.4

Compare Source

Changes
  • Implement Rust FFI wrapper of SMT C (#​16, enable feature smtc to use it)
  • MerkleProof#compile use leaves keys only (#​22)
  • Support extract compiled proof for sub leaves (#​27)
  • Split Store trait into small ones (#​30)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/sparse-merkle-tree-0.x branch from 82e261f to cc1ef71 Compare November 21, 2022 08:26
@renovate renovate bot changed the title fix(deps): update rust crate sparse-merkle-tree to 0.5.4 fix(deps): update rust crate sparse-merkle-tree to 0.6.0 Nov 21, 2022
@renovate renovate bot force-pushed the renovate/sparse-merkle-tree-0.x branch from cc1ef71 to ffd8ff8 Compare November 22, 2022 11:09
@renovate renovate bot changed the title fix(deps): update rust crate sparse-merkle-tree to 0.6.0 fix(deps): update rust crate sparse-merkle-tree to 0.6.1 Nov 22, 2022
@renovate renovate bot force-pushed the renovate/sparse-merkle-tree-0.x branch from ffd8ff8 to 3ecf70b Compare May 5, 2024 11:11
@renovate renovate bot changed the title fix(deps): update rust crate sparse-merkle-tree to 0.6.1 fix(deps): update rust crate sparse-merkle-tree to 0.6.0 May 5, 2024
Copy link
Contributor Author

renovate bot commented May 5, 2024

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path Cargo.toml --package [email protected] --precise 0.6.1
    Updating crates.io index
error: failed to select a version for the requirement `sparse-merkle-tree = "^0.5.3"`
candidate versions found which didn't match: 0.6.1
location searched: crates.io index
required by package `cota-smt v0.1.0 (https://github.com/nervina-labs/cota-smt?tag=0.1.0#d4491021)`
    ... which satisfies git dependency `cota-smt` (locked to 0.1.0) of package `cota-registry-aggregator v0.6.1 (/tmp/renovate/repos/github/nervina-labs/cota-registry-aggregator)`
perhaps a crate was updated and forgotten to be re-vendored?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants