fix: unpin log version

A pinned version forces downstream users to use the same version,
potentially causing versioning conflicts.

Signed-off-by: Florian Hartung <florian.hartung@dlr.de>

Author: florianhartung

Cargo.toml

@@ -11,7 +11,7 @@ resolver = "2"
 env_logger = "0.10.1"
 indexmap = "=2.11.4"                                   # this version has MSRV 1.63, while the next 2.12.0 jumps to MSRV 1.82
 libm = "0.2.8"
-log = "=0.4.22"
+log = "0.4.22"
 serde = { version = "1.0.217", features = ["derive"] }
 serde_json = "1.0.138"
 test-log = { version = "0.2.14", features = ["log"] }

requirements/requirements.sdoc

@@ -136,7 +136,7 @@ RELATIONS:
 UID: REQ-15
 TITLE: Allow log dependency
 STATEMENT: >>>
-The interpreter shall have an optional dependency on the ``log`` crate version ``0.4.22``
+The interpreter shall have an optional dependency on the ``log`` version ``0.4.22`` or later.
 <<<
 RATIONALE: >>>
 Logging is an essential tool to make a system observable, and aid in debugging. Bespoke crate is widely used in the Rust ecosystem and can be attached to any (or no) logging backend. Using conditional compilation, all of the ``log`` crate's footprint in the WASM interpreter (foremost the ``debug``, ``error``, ``info``, ``trace`` and ``warn`` macro) can be expanded to empty statements to avoid **any** run-time impact when opting out of the dependency on ``log``.