A 46e6f46008 fix: stop creating ~/.bash_profile — was destroying system PATH (#1258) ... On Ubuntu/Debian, ~/.bash_profile doesn't exist by default. When bash starts as a login shell (bash -l), it sources the FIRST file it finds from: ~/.bash_profile, ~/.bash_login, ~/.profile. Since only ~/.profile exists, that's what gets sourced — and ~/.profile sets up the standard PATH (/usr/bin, /bin, etc.) and sources ~/.bashrc. Our inject_env_vars_* functions and _finalize_claude_install were writing to ~/.bash_profile and ~/.zprofile (either via touch+append or via for-loop over all rc files). Creating ~/.bash_profile caused bash -l to source it INSTEAD of ~/.profile, completely losing the standard PATH setup. After deployment, even basic commands like `ls` would fail. Fix: Only write to ~/.profile, ~/.bashrc, ~/.zshrc across all clouds (shared, fly, sprite). These are the standard files that work correctly on all Linux distros without breaking the shell initialization chain. Co-authored-by: lab <6723574+louisgv@users.noreply.github.com> Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>		2026-02-16 00:27:28 -08:00
..
common.sh	fix: stop creating ~/.bash_profile — was destroying system PATH (#1258)	2026-02-16 00:27:28 -08:00
github-auth.sh	refactor: decompose ensure_jq and ensure_gh_cli into focused helpers (#994)	2026-02-13 12:14:56 -08:00
key-request.sh	fix: HIGH severity security issues (command injection + weak VNC password) (#1150)	2026-02-14 20:39:48 -05:00