Bump keyring from 10.1 to 25.6.0

[dependabot]

Bumps keyring from 10.1 to 25.6.0.

Changelog

Sourced from keyring's changelog.

v25.6.0

Features

• Avoid logging a warning when config does not specify a backend. (#682)

v25.5.0

Features

• When parsing keyring_path from the config, the home directory is now expanded from ~. (#696)

Bugfixes

• In get_credential, now returns None when the indicated username is not found. (#698)

v25.4.1

Bugfixes

• Fixed ValueError for AnonymousCredentials in CLI. (#694)

v25.4.0

Features

• Refined type spec and interfaces on credential objects. Introduced AnonymousCredential to model a secret without a username. (#689)

v25.3.0

Features

• Deprecated support for empty usernames. Now all backends will reject an empty string as input for the 'username' field when setting a password. Later this deprecation will become a more visible user warning and even later an error. If this warning is triggered in your environment, please consider using a static value (even 'username') or comment in the issue and describe the use-case that demands support for empty usernames. (#668)

... (truncated)

Commits

• a9a7624 Finalize
• 21680c6 Merge pull request #702 from jfly/issue-682
• bf80b69 Add news fragment.
• 1526c17 Don't log a warning when the backend config section is missing
• edaa964 Merge https://github.com/jaraco/skeleton
• 5c34e69 Use extend for proper workaround.
• 1119d7b Merge https://github.com/jaraco/skeleton
• 750a189 Require Python 3.9 or later now that Python 3.8 is EOL.
• e61a9df Include pyproject.toml in ruff.toml.
• db4dfc4jaraco/skeleton#151
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[vincbeck]

This upgrade seems like a big jump. Are we comfortable it is fine if tests are passing or extra testing is required? @potiuk

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.