Closed renovate[bot] closed 2 months ago
[!IMPORTANT]
Review skipped
Review was skipped due to path filters
Files ignored due to path filters (3)
* `Cargo.lock` is excluded by `!**/*.lock`, `!**/*.lock` * `crates/kftray-server/Cargo.toml` is excluded by `!**/*.toml` * `crates/kftray-tauri/Cargo.toml` is excluded by `!**/*.toml`You can disable this status message by setting the
reviews.review_status
tofalse
in the CodeRabbit configuration file.
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
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:
The artifact failure details are included below:
Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path crates/kftui/Cargo.toml --package crossterm@0.27.0 --precise 0.28.1
Updating crates.io index
error: failed to select a version for the requirement `crossterm = "^0.27"`
candidate versions found which didn't match: 0.28.1
location searched: crates.io index
required by package `ratatui-explorer v0.1.1`
... which satisfies dependency `ratatui-explorer = "^0.1.1"` (locked to 0.1.1) of package `kftui v0.13.0 (/tmp/renovate/repos/github/hcavarsan/kftray/crates/kftui)`
This PR contains the following updates:
0.27
->0.28
3.4.4
->3.4.5
0.11.4
->0.11.5
0.1.6
->0.1.7
3.0.4
->3.2.0
0.26
->0.28
1.80.0-alpine3.19
->1.80.1-alpine3.19
1.0.120
->1.0.124
1.39.1
->1.39.2
0.4.13
->0.5.0
Release Notes
crossterm-rs/crossterm (crossterm)
### [`v0.28.1`](https://togithub.com/crossterm-rs/crossterm/blob/HEAD/CHANGELOG.md#Version-0281) #### Fixed π - Fix broken build on linux when using `use-dev-tty` with ([#906](https://togithub.com/crossterm-rs/crossterm/issues/906)) #### Breaking β οΈ - Fix desync with mio and signalhook between repo and published crate. (upgrade to mio 1.0)hwchen/keyring-rs (keyring)
### [`v3.2.0`](https://togithub.com/hwchen/keyring-rs/releases/tag/v3.2.0): : Improve secret-service handling of targets [Compare Source](https://togithub.com/hwchen/keyring-rs/compare/v3.1.0...v3.2.0) As reported in [#201](https://togithub.com/hwchen/keyring-rs/issues/201) and now fixed in [#204](https://togithub.com/hwchen/keyring-rs/issues/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](https://togithub.com/hwchen/keyring-rs/issues/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`](https://togithub.com/hwchen/keyring-rs/releases/tag/v3.1.0): : enhance the CLI [Compare Source](https://togithub.com/hwchen/keyring-rs/compare/v3.0.5...v3.1.0) As reported in [#201](https://togithub.com/hwchen/keyring-rs/issues/201), the CLI had a couple of problems: - It didn't allow empty user names, even on platforms where that's supported. - Its debugging output on `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.ratatui-org/ratatui (ratatui)
### [`v0.28.0`](https://togithub.com/ratatui-org/ratatui/blob/HEAD/CHANGELOG.md#0280---2024-08-07) [Compare Source](https://togithub.com/ratatui-org/ratatui/compare/v0.27.0...v0.28.0) *"If you are what you eat, then I only want to eat the good stuff." β Remy* We are excited to announce the new version of `ratatui` - a Rust library that's all about cooking up TUIs π In this version, we have upgraded to Crossterm 0.28.0, introducing enhanced functionality and performance improvements. New features include GraphType::Bar, lines in bar charts, and enhanced scroll/navigation methods. We have also refined the terminal module and added brand new methods for cursor positions and text operations. β¨ **Release highlights**: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.
π» 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.