Futsch1 / image-sieve

GUI based tool to sort and categorize images written in Rust
GNU General Public License v3.0
129 stars 9 forks source link

Update opener requirement from 0.5 to 0.6 #66

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Updates the requirements on opener to permit the latest version.

Changelog

Sourced from opener's changelog.

[0.6.1] - 2023-04-14

[0.6.0] - 2023-03-27

Added

  • reveal() function, which opens the system's file explorer with the specified file or directory selected. It requires the "reveal" feature to be enabled.

Changed

  • The error message when an executable is missing or otherwise fails to start is now more helpful due to the addition of the OpenError::Spawn variant, which is returned when spawning command(s) fails, and includes the name of the command(s). Before, these errors would be returned as OpenError::Io, which tend to be vague.
  • OpenError is now marked #[non_exhaustive].

Fixed

  • Path handling on Windows has been improved. / separators in relative paths are now accepted.
  • Opening web links on WSL with wslview now works properly.

[0.5.2] - 2023-01-29

Fixed

  • License files are now properly included in the published crate.

[0.5.1] - 2023-01-28

Changed

  • Update xdg-open.

[0.5.0] - 2021-06-11

Added

  • open_browser(), which uses the $BROWSER environment variable before falling back to open().
  • WSL-specific implementation. Previously, WSL used the same implementation as Linux. Now the strategy on WSL is to use the system's wslview command from wslu if available, falling back to the system xdg-open, if available.

Changed

  • On Linux (non-WSL), the system xdg-open is now used if present. Otherwise, the bundled version is used, as before.
  • Avoid blocking the thread on Linux and WSL.

Removed

  • impl From<io::Error> for OpenError.

[0.4.1] - 2019-09-30

Changed

... (truncated)

Commits


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 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)
codecov[bot] commented 1 year ago

Codecov Report

Patch coverage has no change and project coverage change: -0.04 :warning:

Comparison is base (0cb2b87) 76.39% compared to head (6b278e4) 76.36%.

Additional details and impacted files ```diff @@ Coverage Diff @@ ## main #66 +/- ## ========================================== - Coverage 76.39% 76.36% -0.04% ========================================== Files 23 23 Lines 3305 3305 ========================================== - Hits 2525 2524 -1 - Misses 780 781 +1 ``` [see 1 file with indirect coverage changes](https://codecov.io/gh/Futsch1/image-sieve/pull/66/indirect-changes?src=pr&el=tree-more&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=Florian+Fetz)

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.