From e7a5bfd5ab800c6997cff328ef83f9ab45e0eb6b Mon Sep 17 00:00:00 2001 From: Oliver Hamlet Date: Wed, 26 Mar 2025 21:22:20 +0000 Subject: [PATCH] Update loot-condition-interpreter to v5.3.1 --- Cargo.lock | 5 +++-- Cargo.toml | 2 +- README.md | 1 - 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/Cargo.lock b/Cargo.lock index 037cc46d..e8c8e09d 100644 --- a/Cargo.lock +++ b/Cargo.lock @@ -666,8 +666,9 @@ checksum = "30bde2b3dc3671ae49d8e2e9f044c7c005836e7a023ee57cffa25ab82764bb9e" [[package]] name = "loot-condition-interpreter" -version = "5.2.0" -source = "git+https://github.com/loot/loot-condition-interpreter.git?rev=f7d9947fa434037743ce81e2d409184ec0bfb693#f7d9947fa434037743ce81e2d409184ec0bfb693" +version = "5.3.1" +source = "registry+https://github.com/rust-lang/crates.io-index" +checksum = "94d58882c85aba2f4fca0951301b58e03428a8a02e51ccb0cf5f5b28d7869281" dependencies = [ "crc32fast", "esplugin", diff --git a/Cargo.toml b/Cargo.toml index 7db3c744..e0c421ed 100644 --- a/Cargo.toml +++ b/Cargo.toml @@ -32,7 +32,7 @@ members = ["cxx", "ffi-errors", "pyo3"] [workspace.dependencies] esplugin = "6.1.1" libloadorder = "18.3.0" -loot-condition-interpreter = { git = "https://github.com/loot/loot-condition-interpreter.git", rev = "f7d9947fa434037743ce81e2d409184ec0bfb693" } +loot-condition-interpreter = "5.3.1" [profile.release] debug = "limited" diff --git a/README.md b/README.md index 47cb100a..6d3ac4b0 100644 --- a/README.md +++ b/README.md @@ -14,7 +14,6 @@ If this experiment is successful it will probably end up being merged into the l ## Outstanding issues -- It relies on some unreleased improvements to the Rust APIs of libloadorder and loot-condition-interpreter. - It uses more memory than the C++ implementation, and I haven't finished investigating why or if there's anything I can/should do about that. - I'm not very confident about the YAML emitter I've written, it needs more test cases and probably another review against the spec. - The `saphyr` and `saphyr-parser` dependencies that are used to parse metadata YAML have some rough edges, and compared to the other dependencies they are relatively new, unpopular libraries that are maintained by people I've not heard of before, so they may be relatively risky dependencies.