Bryan Helmkamp a1776b7beb fix(test): skip write-key sender assertions when CI bakes the key in ... Two fabro-telemetry sender tests assert that upload/upload_blocking return an error with "SEGMENT_WRITE_KEY not set" -- a claim that only holds when SEGMENT_WRITE_KEY is absent at compile time. The release workflow sets the secret at build time, so these tests now fail under `cargo nextest run --workspace` in release CI (newly exercised after switching the release workflow from `cargo test` to nextest). Guard each assertion with an early return when SEGMENT_WRITE_KEY is compiled in so the test passes in release CI while still verifying the no-key path for every other build. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>		2026-04-17 10:05:39 -04:00
..
crates	fix(test): skip write-key sender assertions when CI bakes the key in	2026-04-17 10:05:39 -04:00
packages/fabro-api-client	refactor(web): rename board column pending → initializing	2026-04-15 09:22:17 -04:00