tftsr-devops_investigation/.gitea/workflows
Shaun Arman fffd0b7400
Some checks failed
PR Review Automation / review (pull_request) Has been cancelled
Test / frontend-tests (pull_request) Has been cancelled
Test / rust-tests (pull_request) Has been cancelled
Test / rust-clippy (pull_request) Has been cancelled
Test / frontend-typecheck (pull_request) Has been cancelled
Test / rust-fmt-check (pull_request) Has been cancelled
fix(ci): unset SODIUM_USE_PKG_CONFIG before cargo builds on all platforms
The libsodium-sys-stable build.rs panics if both SODIUM_LIB_DIR and
SODIUM_USE_PKG_CONFIG are set simultaneously. The runner infrastructure
at 172.0.0.29 has SODIUM_USE_PKG_CONFIG in its container environment
(not traceable to any workflow file or Docker image ENV layer), which
conflicts with the SODIUM_LIB_DIR approach used for cross-compilation.

Explicitly unset SODIUM_USE_PKG_CONFIG in the shell before npm/cargo
runs on all three platforms (linux-amd64, windows-amd64, linux-arm64)
in both release-beta.yml and auto-tag.yml. This is a defensive no-op
when the variable is absent, and a clean fix when it is present.
2026-06-17 20:22:35 -05:00
..
auto-tag.yml chore: merge master into beta — resolve SODIUM_USE_PKG_CONFIG conflict in auto-tag.yml 2026-06-17 20:20:39 -05:00
build-images.yml fix: comprehensive trcaa→tftsr conversion and URL corrections 2026-06-05 15:38:29 -05:00
pr-review.yml ci: update pr-review to leverage anthropics/claude-code pattern 2026-06-10 20:26:31 -05:00
release-beta.yml fix(ci): unset SODIUM_USE_PKG_CONFIG before cargo builds on all platforms 2026-06-17 20:22:35 -05:00
renovate.yaml fix(ci): correct Renovate API endpoint for Gitea 2026-06-09 20:04:55 -05:00
sync-beta.yml feat(ci): auto-sync beta from master after every push 2026-06-13 18:04:37 -05:00
test.yml fix(ci): add libsodium to all build environments 2026-06-17 19:00:06 -05:00