deps: pin nim-ffi to the locked 0.1.3 revision

nim-ffi was required by bare git URL with no version, so a fresh nimble
resolution (as triggered by the bumped nimbledeps cache key) ignored the
nimble.lock pin and floated it to HEAD (0.1.4). nim-ffi 0.1.4 changed
declareLibrary to take a second `libType` argument, so library/declare_lib.nim
fails to compile with a type mismatch and libwaku/liblogosdelivery break.

Pinning the require to the same commit nimble.lock records keeps the
version-less git dependency deterministic across clean resolves, matching
the API the current code targets. Mirrors the existing nim-sds pin style.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
Ivan FB 2026-06-03 11:58:34 +02:00
parent 1e87fb714e
commit 5ccc273ca5
No known key found for this signature in database
GPG Key ID: DF0C67A04C543270

View File

@ -59,7 +59,7 @@ requires "nim >= 2.2.4",
"unittest2"
# Packages not on nimble (use git URLs)
requires "https://github.com/logos-messaging/nim-ffi"
requires "https://github.com/logos-messaging/nim-ffi#06111de155253b34e47ed2aaed1d61d08d62cc1b"
requires "https://github.com/logos-messaging/nim-sds.git#2e9a7683f0e180bf112135fae3a3803eed8490d4"