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.4.0
->0.5.0
4.5.1
->4.5.17
3.4.2
->3.4.5
^2.3.2
->^3.0.0
1.0.197
->1.0.210
1.0.197
->1.0.210
1.0.114
->1.0.128
Release Notes
andreasots/base32 (base32)
v0.5.1
Compare Source
v0.5.0
Compare Source
clap-rs/clap (clap)
v4.5.17
Compare Source
Fixes
v4.5.16
Compare Source
Fixes
derive
feature is missingv4.5.15
Compare Source
Compatiblity
Arg::remove
changed return typesFixes
Arg::remove
return the removed itemv4.5.14
Compare Source
Features
Arg::add
for attaching arbitrary state, like completion hints, toArg
withoutArg
knowing about itv4.5.13
Compare Source
Fixes
#[flatten]
ing an optional#[group(skip)]
v4.5.12
Compare Source
v4.5.11
Compare Source
v4.5.10
Compare Source
v4.5.9
Compare Source
Fixes
v4.5.8
Compare Source
Fixes
v4.5.7
Compare Source
Fixes
num_args
v4.5.6
Compare Source
v4.5.5
Compare Source
Fixes
exclusive
to overriderequired_unless_present
,required_unless_present_any
,required_unless_present_all
v4.5.4
Compare Source
Fixes
#[arg(id)]
attributes againv4.5.3
Compare Source
Internal
heck
v4.5.2
Compare Source
Fixes
Detegr/rust-ctrlc (ctrlc)
v3.4.5
Compare Source
v3.4.4
Compare Source
nix
0.27 -> 0.28MSRV 1.63.0 -> 1.69.0
v3.4.3
Compare Source
hwchen/keyring-rs (keyring)
v3.2.1
: : Re-enable access to v1 credentialsCompare Source
The v3.2.0 release, which fixed #204, had an unfortunate side effect: it broke compatibility with credentials that were originally written by a v1.x release (see #207). This bug-fix release restores that compatibility.
With this change, the CLI changes in v3.2.0 have been reverted, because they are no longer necessary.
v3.2.0
: : Improve secret-service handling of targetsCompare Source
As reported in #201 and now fixed in #204, the secret-service credential store implementation could not disambiguate credentials that were created with different targets unless the collections containing those targets had already been unlocked.
The fix for this issue introduces a compatibility break: secret-service credentials created by the keyring v1 implementation, which were readable using platform-independent code in keyring v2, are no longer readable without using platform-specific code in v3. The necessary platform-specific code is very simple, and it has been added to the CLI (both for documentation purposes and to allow the CLI to access v1 credentials). The comments in issue #204 explain why the decision was made to add this secret-service-specific compatibility break; these include the fact that keyring v2 was released 18 months ago so only those users who haven't changed their password in a very long time would still have a v1 credential in their secret-service store.
The README has been updated to address this compatibility break and to provide recommendations for keyring clients who want to update their code to make sure users with old credentials are not impacted.
v3.1.0
: : enhance the CLICompare Source
As reported in #201, the CLI had a couple of problems:
Ambiguous
errors provided no information about the underlying platform credentials.The first issue was just a bug, now fixed.
The second issue stemmed from the fact that platform-independent code couldn't get at the details of the underlying platform-specific credentials. To fix this, the CredentialAPI had to be extended to provide access to the underlying platform credential's implementation of the
std::fmt::Debug
trait, and each of the keying credential stores extended to implement the new API.To make this API extension backward-compatible, a default implementation was provided that did what the former code did: it revealed nothing. But that allows this release to be a SerVer-compatible dot release, rather than a major release.
v3.0.5
: : update docs and clean up dead codeCompare Source
As reported in #132, using the secret-service asynchronously via the keyring wrapper can lead to deadlocks. The docs have been updated to make this clear, and a recommendation has been added to use the
sync-secret-service
feature so as to avoid any issues related to async runtimes, even if the calling app may already be asynchronous.While this fix was being made, it was discovered that new clippy lints in Rust 1.80 had been added. These lints revealed some dead code related to windows testing, and some documentation that was "legal" per the markdown spec but slightly ambiguous in intent. Both of these other issues were also fixed.
There are no code changes in this release relative to v3.0.4.
v3.0.4
: : expose cross-platform module aliasCompare Source
As reported in #197, there's no way for a client to access an instance of the default credential builder with platform-independent code. This releases fixes that oversight, and provides an example as part of the documentation of the
credential
module.v3.0.3
: : Fix feature linux-nativeCompare Source
Earlier releases didn't correctly use the keyring when the
linux-native
feature was specified. This release does.Thanks to @Brooooooklyn for finding this issue!
v3.0.2
Compare Source
set_secret
andget_secret
v3.0.1
Compare Source
Sync
trait on errors.v3.0.0
Compare Source
dbus-secret-service
dependency to allow use on *n*x without an async runtimev2.3.3
: : Updates for Rust 1.78Rust 1.78 introduced a new clippy check and better guards on Windows when making slices from raw bytes. These changes required one small change in the platform-independent code and two small changes in the Windows-specific code.
serde-rs/serde (serde)
v1.0.210
Compare Source
IpAddr
andSocketAddr
in no-std mode on Rust 1.77+ (#2816, thanks @MathiasKoch)serde::ser::StdError
andserde::de::StdError
equivalent tocore::error::Error
on Rust 1.81+ (#2818)v1.0.209
Compare Source
v1.0.208
Compare Source
flatten
field (#2802, thanks @jonhoo)v1.0.207
Compare Source
flatten
attribute andskip_serializing
/skip_deserializing
(#2795, thanks @Mingun)v1.0.206
Compare Source
flatten
attribute inside of enums (#2567, thanks @Mingun)v1.0.205
Compare Source
v1.0.204
Compare Source
v1.0.203
Compare Source
v1.0.202
Compare Source
v1.0.201
Compare Source
v1.0.200
Compare Source
v1.0.199
Compare Source
forward_to_deserialize_any!
is used on an enum withError
variant (#2732, thanks @aatifsyed)v1.0.198
Compare Source
Saturating<T>
(#2709, thanks @jbethune)serde-rs/json (serde_json)
v1.0.128
Compare Source
v1.0.127
Compare Source
v1.0.126
Compare Source
v1.0.125
Compare Source
v1.0.124
Compare Source
v1.0.123
Compare Source
v1.0.122
Compare Source
json!
in no-std crates (#1166)v1.0.121
Compare Source
v1.0.120
Compare Source
indexmap
dependency (#1152, thanks @cforycki)v1.0.119
Compare Source
serde_json::Map::shift_insert
(#1149, thanks @joshka)v1.0.118
Compare Source
v1.0.117
Compare Source
v1.0.116
Compare Source
v1.0.115
Compare Source
Configuration
📅 Schedule: Branch creation - "before 4am on Monday" (UTC), 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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.