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 secrecy to 0.10 - autoclosed #152

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Sep 18, 2024

This PR contains the following updates:

Package Type Update Change
secrecy (source) dependencies minor 0.8 -> 0.10

Release Notes

iqlusioninc/crates (secrecy)

v0.10.1

Added
  • Impl Clone for SecretString (#​1217)

v0.10.0

This release represents a significant redesign of the secrecy crate. We will update this section
with upgrade instructions based on feedback from people upgrading, as it's been a long time since
the previous release, and this release includes a number of breaking changes.

The most notable change is the generic Secret<T> type has been removed: instead use SecretBox<T>
which stores secrets on the heap instead of the stack. Many of the other changes fall out of this
change and things which were previously type aliases of Secret<T> are now type aliases of
SecretBox<T>.

This unfortunately means this crate no longer has support for "heapless" no_std targets. We don't
have a good solution for these targets, which was a motivation for this change in the first place.

Added
Changed
  • Rust 2021 edition upgrade (#​889)
  • MSRV 1.60 (#​1105)
  • SecretBox<T> is now a newtype rather than a type alias of `Secret<Box> (#​1140)
  • SecretString is now a type alias for SecretBox<str> (#​1213)
  • Disable serde default features (#​1194)
Removed
  • alloc feature: now a hard dependency (#​1140)
  • bytes crate integration: no replacement (#​1140)
  • DebugSecret trait: no replacement (#​1140)
  • Secret<T>: use SecretBox<T> instead (#​1140)

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.

Copy link
Contributor Author

renovate bot commented Sep 18, 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.10.0
    Updating crates.io index
error: failed to select a version for the requirement `secrecy = "^0.8.0"`
candidate versions found which didn't match: 0.10.0
location searched: crates.io index
required by package `octocrab v0.35.0`
    ... which satisfies dependency `octocrab = "^0.35.0"` (locked to 0.35.0) of package `bors v0.1.0 (/tmp/renovate/repos/github/rust-lang/bors)`

@renovate renovate bot changed the title fix(deps): update rust crate secrecy to 0.10 fix(deps): update rust crate secrecy to 0.10 - autoclosed Oct 11, 2024
@renovate renovate bot closed this Oct 11, 2024
@renovate renovate bot deleted the renovate/secrecy-0.x branch October 11, 2024 09:53
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