crowdsec-firewall-bouncer: fix version in binary

[rikroe]

📦 Package Details

Maintainer: Kerma Gérald gandalf@gk2.net / @ne20002

Description:
Package version string was changed in upstream and binary did not report any build info anymore.
This included upstream LAPI version reporting.

---

🧪 Run Testing Details

• OpenWrt Version: SNAPSHOT
• OpenWrt Target/Subtarget: mediatek/filogic
• OpenWrt Device: GL.iNet GL-MT6000

root@GL-MT6000:~# /usr/bin/cs-firewall-bouncer --version
version: v0.0.34-openwrt-0.0.34-1
BuildDate: 2026-01-01_13:46:35
GoVersion: 1.25.4
Platform: linux

Also reports correctly to crowdsec LAPI:

0b855931ddb8:/# cscli bouncer list
───────────────────────────────────────────────────────────────────────────────────────────────────────
 Name       ...   Last API pull         Type                       Version                   Auth Type
───────────────────────────────────────────────────────────────────────────────────────────────────────
 openwrt    ...   2026-01-01T14:03:46Z  crowdsec-firewall-bouncer  v0.0.34-openwrt-0.0.34-1  api-key
───────────────────────────────────────────────────────────────────────────────────────────────────────

---

✅ Formalities

• I have reviewed the CONTRIBUTING.md file for detailed contributing guidelines.

If your PR contains a patch:

• It can be applied using git am
• It has been refreshed to avoid offsets, fuzzes, etc., using

  make package/<your-package>/refresh V=s

• It is structured in a way that it is potentially upstreamable
  _{(e.g., subject line, commit description, etc.)
  We must try to upstream patches to reduce maintenance burden.}

[ne20002]

Shouldn't this be fixed in the upstream project?

[rikroe]

As far as I can tell, they made the active decision to switch over to https://github.com/crowdsecurity/go-cs-lib:

• use go-cs-lib crowdsecurity/cs-firewall-bouncer#287 (first change)
• Support option "retry_initial_connect" crowdsecurity/cs-firewall-bouncer#310 (adjustment)