Skip to content

fix(ci): use $GITHUB_PATH for lux bin in release workflow - #29

Merged
tkolleh merged 1 commit into
mainfrom
fix/release-path-bug
Apr 5, 2026
Merged

fix(ci): use $GITHUB_PATH for lux bin in release workflow#29
tkolleh merged 1 commit into
mainfrom
fix/release-path-bug

Conversation

@tkolleh

@tkolleh tkolleh commented Apr 5, 2026

Copy link
Copy Markdown
Owner

Summary

  • Replace broken env: PATH override with idiomatic $GITHUB_PATH mechanism
  • Fixes just: command not found error that has blocked every release since v1.13.0

Root Cause

The Build Executable step had:

env:
  PATH: "${{ env.HOME }}/.lux/5.4/bin:${PATH}"

Two bugs:

  1. ${{ env.HOME }} → empty string (HOME is a shell var, not env context)
  2. ${PATH} → literal string, NOT expanded in env: context

Result: PATH became /.lux/5.4/bin:${PATH} (literal), replacing the entire system PATH and removing /usr/local/bin where just was installed.

Fix

  • Add Add Lux bin to PATH step using echo "$HOME/.lux/5.4/bin" >> "$GITHUB_PATH"
  • Remove broken PATH from env: block
  • Remove redundant export PATH from run: block

The Build Executable step was failing with 'just: command not found'
because the env: PATH override replaced the entire system PATH with a
broken literal string (env.HOME is empty, ${PATH} is not expanded).

Use $GITHUB_PATH to add the lux bin directory for all subsequent steps
instead of overriding PATH in the env: block. This is the idiomatic
GitHub Actions approach for PATH manipulation.
@tkolleh
tkolleh merged commit 54fe971 into main Apr 5, 2026
2 checks passed
@tkolleh
tkolleh deleted the fix/release-path-bug branch April 5, 2026 11:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant