fix(ci): use env -u instead of unset to drop SODIUM_USE_PKG_CONFIG #113
No reviewers
Labels
No Label
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: sarman/tftsr-devops_investigation#113
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "fix/env-u-sodium"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
unset SODIUM_USE_PKG_CONFIGin therun:script did not fix the panic. The act_runner at172.0.0.29re-injects runner-level environment variables at the process level, meaningbash unsetclears the var from the shell but it comes back when the cargo subprocess is spawned.Fix
Replace
unset+ build command withenv -u SODIUM_USE_PKG_CONFIG CI=true npx tauri build. Theenv -uflag removes the variable from the child process environment at theexec()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.ymlandauto-tag.yml:linux-amd64:SODIUM_LIB_DIR=/usr/lib/x86_64-linux-gnu+env -uwindows-amd64:SODIUM_LIB_DIR=/usr/x86_64-w64-mingw32/lib+env -ulinux-arm64:SODIUM_LIB_DIR=/usr/lib/aarch64-linux-gnu+env -u