• v0.3.3 15e7039d37

    v0.3.3
    Some checks failed
    CI / cargo fmt (push) Successful in 29s
    Release Build / Generate Version (push) Successful in 20s
    CI / cargo clippy (push) Successful in 47s
    CI / cargo test (push) Failing after 2m47s
    Release Build / Build linux-x86_64 (push) Successful in 4m34s
    Release Build / Build linux-aarch64 (push) Successful in 5m16s
    Release Build / Build windows-x86_64 (push) Successful in 5m29s
    Release Build / Create Forgejo Release (push) Failing after 1m3s
    Stable

    buildagent released this 2026-06-04 14:29:17 +02:00 | 20 commits to master since this release

    Fix

    Release builds previously set panic = "abort", which silently turned the catch_unwind guard in parse_with_plugin into a no-op: a panicking tree-sitter grammar would SIGABRT the whole long-lived daemon instead of being caught and recorded as a parse_error row. This release switches [profile.release] to panic = "unwind" so that resilience holds in production. The size optimizations (lto, codegen-units, strip) are unchanged.

    Verified end-to-end under the real release profile: a panicking plugin is caught and recorded (IndexStats.parse_errors=1, exit 0); a negative control under panic = "abort" aborts with exit 134, confirming the regression was real.

    Note: this regression is invisible to cargo test — the test harness forces panic = "unwind" regardless of profile.

    Changes: v0.3.2...v0.3.3

    Downloads