-
Notifications
You must be signed in to change notification settings - Fork 42
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 secrecy to 0.10.3 #6722
Open
oxide-renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/secrecy-0.x
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
oxide-renovate
bot
added
the
dependencies
Pull requests that update a dependency file
label
Sep 28, 2024
|
oxide-renovate
bot
force-pushed
the
renovate/secrecy-0.x
branch
2 times, most recently
from
October 5, 2024 03:07
719a0d0
to
2ea7c53
Compare
oxide-renovate
bot
force-pushed
the
renovate/secrecy-0.x
branch
from
October 10, 2024 03:07
2ea7c53
to
c2e32ed
Compare
oxide-renovate
bot
changed the title
Update Rust crate secrecy to 0.10.2
Update Rust crate secrecy to 0.10.3
Oct 10, 2024
oxide-renovate
bot
force-pushed
the
renovate/secrecy-0.x
branch
3 times, most recently
from
October 16, 2024 03:13
e7acf62
to
348037f
Compare
oxide-renovate
bot
force-pushed
the
renovate/secrecy-0.x
branch
from
November 1, 2024 03:03
348037f
to
354eb8b
Compare
oxide-renovate
bot
force-pushed
the
renovate/secrecy-0.x
branch
3 times, most recently
from
November 14, 2024 06:50
6702a93
to
471840e
Compare
oxide-renovate
bot
force-pushed
the
renovate/secrecy-0.x
branch
2 times, most recently
from
November 22, 2024 04:19
791c2e7
to
0437550
Compare
oxide-renovate
bot
force-pushed
the
renovate/secrecy-0.x
branch
3 times, most recently
from
December 19, 2024 04:02
bf71429
to
3b34420
Compare
oxide-renovate
bot
force-pushed
the
renovate/secrecy-0.x
branch
from
December 21, 2024 04:18
3b34420
to
71dd48b
Compare
oxide-renovate
bot
force-pushed
the
renovate/secrecy-0.x
branch
4 times, most recently
from
January 18, 2025 04:18
578e177
to
fbe8604
Compare
oxide-renovate
bot
force-pushed
the
renovate/secrecy-0.x
branch
from
January 25, 2025 04:19
fbe8604
to
4b3cf78
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.8.0
->0.10.3
Release Notes
iqlusioninc/crates (secrecy)
v0.10.3
Added
SecretSlice
s cloneable (#1236)From<&str>
forSecretString
(#1237)v0.10.2
Added
Deserialize
forSecretString
(#1220)v0.10.1
Added
Clone
forSecretString
(#1217)v0.10.0
This release represents a significant redesign of the
secrecy
crate. We will update this sectionwith 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 useSecretBox<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 ofSecretBox<T>
.This unfortunately means this crate no longer has support for "heapless"
no_std
targets. We don'thave a good solution for these targets, which was a motivation for this change in the first place.
Added
SecretBox::{init_with, try_init_with}
(#1212)SecretBox::init_with_mut
(#1213)?Sized
bounds forSecretBox
(#1213)SecretSlice<T>
(#1214)Changed
SecretBox<T>
is now a newtype rather than a type alias of `Secret<Box> (#1140)SecretString
is now a type alias forSecretBox<str>
(#1213)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>
: useSecretBox<T>
instead (#1140)Configuration
📅 Schedule: Branch creation - "after 8pm,before 6am" in timezone America/Los_Angeles, Automerge - "after 8pm,before 6am" in timezone America/Los_Angeles.
🚦 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.
This PR has been generated by Renovate Bot.