chore(deps): update rust crate secrecy to 0.10.0

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
secrecy (source)	dependencies	minor	0.8.0 -> 0.10.0

---

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

• SecretBox::{init_with, try_init_with} (#​1212)
• SecretBox::init_with_mut (#​1213)
• ?Sized bounds for SecretBox (#​1213)
• SecretSlice<T> (#​1214)

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 - "before 4am" in timezone America/Sao_Paulo, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, 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]

⚠️ 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 crates/kftray-portforward/Cargo.toml --package secrecy@0.8.0 --precise 0.10.2
    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.2
location searched: crates.io index
required by package `kube-client v0.94.2`
    ... which satisfies dependency `kube-client = "=0.94.2"` (locked to 0.94.2) of package `kube v0.94.2`
    ... which satisfies dependency `kube = "^0.94.2"` (locked to 0.94.2) of package `kftray-tauri v0.14.4 (/tmp/renovate/repos/github/hcavarsan/kftray/crates/kftray-tauri)`

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  -- I pushed a fix in commit <commit_id>, please review it.
  -- Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  -- @coderabbitai generate unit testing code for this file.
  -- @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  -- @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  -- @coderabbitai read src/utils.ts and generate unit testing code.
  -- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  -- @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.