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

Update Rust crate sapling to 0.4 #453

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 27, 2024

This PR contains the following updates:

Package Type Update Change
sapling dependencies minor 0.3 -> 0.4

Release Notes

zcash/sapling-crypto (sapling)

v0.4.0

Compare Source

Added
  • Support for Partially-Created Zcash Transactions:
    • sapling_crypto::builder::Builder::build_for_pczt
    • sapling_crypto::pczt module.
  • sapling_crypto::bundle::EffectsOnly
  • sapling_crypto::keys:
    • SpendAuthorizingKey::to_bytes
    • SpendValidatingKey::to_bytes
  • sapling_crypto::value::ValueSum::to_raw
  • sapling_crypto::zip32::DiversifiableFullViewingKey::to_internal_fvk
Fixed
  • sapling_crypto::prover::OutputProver::prepare_circuit now takes esk as an
    sapling_crypto::keys::EphemeralSecretKey, matching the existing public APIs
    that expose it.
Changed
  • sapling_crypto::builder:
    • SpendInfo::new now takes a FullViewingKey instead of a
      ProofGenerationKey.
    • Builder::add_spend now takes a FullViewingKey instead of an
      &ExtendedSpendingKey.
    • Builder::build and bundle now take an &[ExtendedSpendingKey] argument.
    • Error has new variants:
      • MissingSpendingKey
      • PcztRequiresZip212
      • WrongSpendingKey
  • sapling_crypto::bundle::SpendDescriptionV5::into_spend_description now
    supports any Authorization for which the SpendDescription itself is fully
    authorized.

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 added the dependencies Pull requests that update a dependency file label Dec 27, 2024
Copy link
Contributor Author

renovate bot commented Dec 27, 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: src/nerdbank-zcash-rust/Cargo.lock
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path src/nerdbank-zcash-rust/Cargo.toml --workspace
    Updating crates.io index
error: failed to get `zcash_address` as a dependency of package `nerdbank-zcash-rust v0.1.0 (/tmp/renovate/repos/github/nerdcash/Nerdbank.Cryptocurrencies/src/nerdbank-zcash-rust)`

Caused by:
  failed to load source for dependency `zcash_address`

Caused by:
  Unable to update /tmp/renovate/repos/github/nerdcash/Nerdbank.Cryptocurrencies/external/librustzcash/components/zcash_address

Caused by:
  failed to read `/tmp/renovate/repos/github/nerdcash/Nerdbank.Cryptocurrencies/external/librustzcash/components/zcash_address/Cargo.toml`

Caused by:
  No such file or directory (os error 2)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants