Replace `directories-next` dependency with `directories` (#4661)

`directories-next` was created because `directories` was not maintained
at the time. However, `directories` has gotten active maintainership
since, and it has received more updates than `directories-next`.

`directories` also has more recent downloads than its `next`
counterpart, so it might make sense to switch to it, to avoid
unnecessary duplicate dependencies, where a project depends transitively
on both `directories` and `directories-next`.

The main question is whether we depend on any specific behavior from
`directories-next`.

1 files changed, 1 insertions, 1 deletions

diff --git a/deny.toml b/deny.toml
index 02a9cdb0..cb32a6f9 100644
--- a/deny.toml
+++ b/deny.toml
@@ -52,7 +52,7 @@ skip = [
   { name = "libloading" },     # wgpu-hal itself depends on 0.8 while some of its dependencies, like ash and d3d12, depend on 0.7
   { name = "memoffset" },      # tiny dependency
   { name = "quick-xml" },      # old version via wayland-scanner
-  { name = "redox_syscall" },  # old version via directories-next
+  { name = "redox_syscall" },  # old version via winit
   { name = "spin" },           # old version via ring through rusttls and other libraries, newer for wgpu.
   { name = "time" },           # old version pulled in by unmaintianed crate 'chrono'
   { name = "windows" },        # old version via accesskit_windows