Skip to content

fix(deps): update rust crate keyring to v4 - #532

Open
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/keyring-4.x
Open

fix(deps): update rust crate keyring to v4#532
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/keyring-4.x

Conversation

@renovate

@renovate renovate Bot commented Apr 26, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
keyring (source) dependencies major 34.1.5

Release Notes

open-source-cooperative/keyring-rs (keyring)

v4.1.5: : Compatibility release

Compare Source

Rust 1.97 introduced a new clippy lint that fired on the CLI example. This release fixes that problem.

This release also takes the recent bug fix to the Apple native credential store.

There are no functional changes in this release.

What's Changed

Full Changelog: open-source-cooperative/keyring-rs@v4.1.4...v4.1.5

v4.1.4: : fix yanked version v4.1.3

Compare Source

This is an emergency release fixing the DOA bug #​335 reported by @​raph-ADF (thanks!).

What's Changed

Full Changelog: open-source-cooperative/keyring-rs@v4.1.3...v4.1.4

v4.1.3: (YANKED): better error reporting

Compare Source

The only functional change is better error reporting on the first call to Entry::new if the default store fails to instantiate (thanks @​eirnym).

NOTE: This release has been yanked because of #​335. It has been replaced by v4.1.4.

What's Changed

Full Changelog: open-source-cooperative/keyring-rs@v4.1.2...v4.1.3

v4.1.2: : coverage for more *nix OSes

Compare Source

This release allows use of secret-service crate on all *nix OSes - thanks @​eirnym!

There are no functional changes.

What's Changed

New Contributors

Full Changelog: open-source-cooperative/keyring-rs@v4.1.1...v4.1.2

v4.1.1: : documentation fixes

Compare Source

This release fixes the problems with documentation and public markers in v4.0. There are no functional changes.

What's Changed

Full Changelog: open-source-cooperative/keyring-rs@v4.1.0...v4.1.1

v4.1.0: : Restore keyring v1-like standalone functionality

Compare Source

This release moves the CLI binary out to an example so we can lose a lot of dependencies that aren't needed to use credential stores.

In addition, it recreates the v1 (and v2/v3) functionality of providing an Entry object that any app can use (without special features or initialization) to manage text and binary secrets. This is provided by the v1 feature, which is the default. (This change fixes #​317.)

The ability to use any credential store is still preserved in the cli module but the cli feature which exposes it is not in the default feature set.

Strictly speaking, these changes are probably SemVer-significant. But since there are few to no clients of the existing library functionality, we're calling this a patch release.

What's Changed

Full Changelog: open-source-cooperative/keyring-rs@v4.0.1...v4.1.0

v4.0.1: : sample code bug fix for iOS

Compare Source

This release has just one change: a bug fix in the sample code for iOS that was preventing use of the protected data store.

What's Changed

Full Changelog: open-source-cooperative/keyring-rs@v4.0.0...v4.0.1

v4.0.0: : general release of keyring v4

Compare Source

With keyring-core at 1.0, and all the included credential stores using the 1.0 release, it's finally time to release the "new" keyring which is just a sample app. See the wiki for all the details of the new architecture.

IMPORTANT: Apps that use keyring-compatible credential stores should not be relying on this release! They should instead be relying on the v1 release of keyring-core.

What's Changed

New Contributors

Full Changelog: open-source-cooperative/keyring-rs@v3.6.3...v4.0.0


Configuration

📅 Schedule: (UTC)

  • 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 commented Apr 26, 2026

Copy link
Copy Markdown
Contributor Author

⚠️ 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 --workspace
    Updating crates.io index
error: failed to select a version for `keyring`.
    ... required by package `oktaws v0.24.0 (/tmp/renovate/repos/github/jonathanmorley/oktaws)`
versions that meet the requirements `^4.1.5` are: 4.1.5

package `oktaws` depends on `keyring` with feature `apple-native` but `keyring` does not have that feature.
help: available features: android-native-keyring-store, apple-native-keyring-store, cli, db-keystore, dbus-secret-service-keyring-store, default, linux-keyutils-keyring-store, v1, windows-native-keyring-store, zbus-secret-service-keyring-store


failed to select a version for `keyring` which could resolve this conflict

@renovate
renovate Bot force-pushed the renovate/keyring-4.x branch 2 times, most recently from d1f5742 to 99e1164 Compare May 18, 2026 14:48
@renovate renovate Bot changed the title Update Rust crate keyring to v4 fix(deps): update rust crate keyring to v4 May 22, 2026
@renovate
renovate Bot force-pushed the renovate/keyring-4.x branch 2 times, most recently from 88a22f2 to 606ba72 Compare June 21, 2026 06:09
@renovate
renovate Bot force-pushed the renovate/keyring-4.x branch 2 times, most recently from 0dd205a to 61ba651 Compare July 6, 2026 20:09
@renovate
renovate Bot force-pushed the renovate/keyring-4.x branch from 61ba651 to 35a0e19 Compare July 14, 2026 20:53
@renovate
renovate Bot force-pushed the renovate/keyring-4.x branch from 35a0e19 to 569aa04 Compare July 21, 2026 03:15
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