fix(ci): use env -u instead of unset to drop SODIUM_USE_PKG_CONFIG #113

Merged
sarman merged 1 commits from fix/env-u-sodium into beta 2026-06-18 02:09:04 +00:00
Owner

Problem

unset SODIUM_USE_PKG_CONFIG in the run: script did not fix the panic. The act_runner at 172.0.0.29 re-injects runner-level environment variables at the process level, meaning bash unset clears the var from the shell but it comes back when the cargo subprocess is spawned.

Fix

Replace unset + build command with env -u SODIUM_USE_PKG_CONFIG CI=true npx tauri build. The env -u flag removes the variable from the child process environment at the exec() call level — it is immune to runner re-injection because it controls the exec environment directly, not the shell state.

Scope

All three non-macOS platforms in both release-beta.yml and auto-tag.yml:

  • linux-amd64: SODIUM_LIB_DIR=/usr/lib/x86_64-linux-gnu + env -u
  • windows-amd64: SODIUM_LIB_DIR=/usr/x86_64-w64-mingw32/lib + env -u
  • linux-arm64: SODIUM_LIB_DIR=/usr/lib/aarch64-linux-gnu + env -u
## Problem `unset SODIUM_USE_PKG_CONFIG` in the `run:` script did not fix the panic. The act_runner at `172.0.0.29` re-injects runner-level environment variables at the process level, meaning `bash unset` clears the var from the shell but it comes back when the cargo subprocess is spawned. ## Fix Replace `unset` + build command with `env -u SODIUM_USE_PKG_CONFIG CI=true npx tauri build`. The `env -u` flag removes the variable from the child process environment at the `exec()` call level — it is immune to runner re-injection because it controls the exec environment directly, not the shell state. ## Scope All three non-macOS platforms in both `release-beta.yml` and `auto-tag.yml`: - `linux-amd64`: `SODIUM_LIB_DIR=/usr/lib/x86_64-linux-gnu` + `env -u` - `windows-amd64`: `SODIUM_LIB_DIR=/usr/x86_64-w64-mingw32/lib` + `env -u` - `linux-arm64`: `SODIUM_LIB_DIR=/usr/lib/aarch64-linux-gnu` + `env -u`
sarman added 1 commit 2026-06-18 02:07:47 +00:00
fix(ci): use env -u instead of unset to drop SODIUM_USE_PKG_CONFIG
Some checks failed
PR Review Automation / review (pull_request) Has been cancelled
Test / rust-clippy (pull_request) Has been cancelled
Test / frontend-typecheck (pull_request) Has been cancelled
Test / rust-tests (pull_request) Has been cancelled
Test / rust-fmt-check (pull_request) Has been cancelled
Test / frontend-tests (pull_request) Has been cancelled
0536a6767b
bash unset modifies the current shell's environment but the act_runner
at 172.0.0.29 re-injects runner-level environment variables before each
cargo invocation, making unset ineffective. env -u removes the variable
from the child process's environment at the exec() level, bypassing any
runner re-injection entirely.

Applies to all three non-macOS platforms (linux-amd64, windows-amd64,
linux-arm64) in both release-beta.yml and auto-tag.yml.
sarman merged commit cd7bea9ec5 into beta 2026-06-18 02:09:04 +00:00
sarman deleted branch fix/env-u-sodium 2026-06-18 02:09:04 +00:00
Sign in to join this conversation.
No reviewers
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: sarman/tftsr-devops_investigation#113
No description provided.