* fix(ci): fix three coverage workflow failures
1. Migration ordering: glob `V*.sql` sorted V10 before V1 (ASCII '0' < '_').
Use `sort -V` for correct numeric ordering.
2. Missing WASM channels: telegram_auth_integration tests need the Telegram
WASM binary. Add wasm32-wasip2 target, cargo-component, and
build-wasm-extensions.sh to both coverage and e2e-coverage jobs
(matching test.yml).
3. E2E shell quoting: `cargo llvm-cov show-env` outputs shell-quoted values
(KEY='value') but GITHUB_ENV expects unquoted KEY=value. Strip single
quotes with sed before appending.
[skip-regression-check]
Co-Authored-By: Claude Opus 4.6 <[email protected]>
* fix(ci): address PR review feedback on coverage workflow
- Migration loop: use readarray + printf | sort -V instead of $(ls)
to avoid word-splitting on filenames
- cargo-component install: check if already installed first, don't
mask failures with || true
- show-env quote stripping: use targeted regex to strip only wrapping
quotes (KEY='value' -> KEY=value) instead of removing all quotes
[skip-regression-check]
Co-Authored-By: Claude Opus 4.6 <[email protected]>
* fix: skip telegram_auth_integration tests when WASM module not built
Replace panicking assert! with a require_telegram_wasm!() macro that
gracefully skips tests when the Telegram WASM binary hasn't been compiled.
This ensures the test suite passes across all configurations (with and
without wasm32-wasip2 target), while still running the tests in CI where
the WASM channels are built.
[skip-regression-check]
Co-Authored-By: Claude Opus 4.6 <[email protected]>
* fix: panic in CI when telegram WASM module missing, skip locally
- require_telegram_wasm!() now checks the CI env var: panics in CI
(so a broken WASM build step fails loudly) but skips locally
- fs::read error now includes the file path for better diagnostics
[skip-regression-check]
Co-Authored-By: Claude Opus 4.6 <[email protected]>
---------
Co-authored-by: Claude Opus 4.6 <[email protected]>
