chore(deps): Drop patch to use custom chrono repo (vectordotdev#18567)

We had set up a custom `chrono` repo to be able to use the crate without enabling the `oldtime` feature, which in turn pulled in the `time` crate that was the subject of a vulnerability issue. With the latest `chrono` release, it no longer depends on the `time` crate, so the patch is no longer needed.
aholmberg · Sep 14, 2023 · 6c34cd5 · 6c34cd5
1 parent 0f90c39
commit 6c34cd5
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 4 deletions.
diff --git a/Cargo.lock b/Cargo.lock
diff --git a/Cargo.toml b/Cargo.toml
@@ -379,9 +379,6 @@ wiremock = "0.5.19"
 zstd = { version = "0.12.4", default-features = false }
 
 [patch.crates-io]
-# Removes dependency on `time` v0.1
-# https://github.com/chronotope/chrono/pull/578
-chrono = { git = "https://github.com/vectordotdev/chrono.git", tag = "v0.4.30-no-default-time-1" }
 # The upgrade for `tokio-util` >= 0.6.9 is blocked on https://github.com/vectordotdev/vector/issues/11257.
 tokio-util = { git = "https://github.com/vectordotdev/tokio", branch = "tokio-util-0.7.8-framed-read-continue-on-error" }
 nix = { git = "https://github.com/vectordotdev/nix.git", branch = "memfd/gnu/musl" }