Describe the feature
I posted previously about this on the rocksdb backend.
Basically I was hoping we could relax the librocksdb-sys version, since it was blocking an important bug fix. Now it seems that the Rust 1.75 pinned versions crate has been removed and the librockdb-sys dependency for the rocksdb backend is just "0.17.1" allowing upgrade to .3 to fix the bug.
However this filesystem backend plugin still has "=0.17.1".
It seems that, if the rocksdb backend could use a newer version, the filesystem backend could too, right?
I understand Zenoh needs to be able to run on Rust 1.75, but couldn't that requirement be imposed and checked in a different way?
Describe the feature
I posted previously about this on the rocksdb backend.
Basically I was hoping we could relax the librocksdb-sys version, since it was blocking an important bug fix. Now it seems that the Rust 1.75 pinned versions crate has been removed and the librockdb-sys dependency for the rocksdb backend is just "0.17.1" allowing upgrade to .3 to fix the bug.
However this filesystem backend plugin still has "=0.17.1".
It seems that, if the rocksdb backend could use a newer version, the filesystem backend could too, right?
I understand Zenoh needs to be able to run on Rust 1.75, but couldn't that requirement be imposed and checked in a different way?