Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
Mirrored from https://github.com/Camo67/composio.git
Synced Nov 21, 17:15 UTC
ci(cli): probe the health-check login shell with a clean environment
The bash -ilc probe inherited the step PATH, which already contains ~/.local/bin via GITHUB_PATH and Ubuntu's skel ~/.profile, so a regression in the bash login-file write could not turn the canary red. Run the probe under env -i with a bare PATH, mirroring the harness's assert_login_bash_path, and additionally assert the managed block in the login-mode startup file the login shell actually reads.
jkomyno committed
Aug 3, 2026 at 20:55 UTC
16bb6a7f2267cf1fe5e6422cfba5720e817be4d6
1 file changed
+25
-1
.github/workflows/cli.install-health-check.yml
+25
-1
@@ -104,8 +104,32 @@ jobs:
104
exit 1
105
fi
106
107
+ # Assert the login-mode startup file (the file a login bash actually reads —
108
+ # ~/.bashrc is not it) also carries the managed block. Mirrors install.sh's
109
+ # bash_login_path_file selection: first existing of ~/.bash_profile or
110
+ # ~/.bash_login, else the ~/.bash_profile the installer creates.
111
+ if [ ! -f "$HOME/.bash_profile" ] && [ -f "$HOME/.bash_login" ]; then
112
+ login_file="$HOME/.bash_login"
113
+ else
114
+ login_file="$HOME/.bash_profile"
115
+ fi
116
+ if grep -Fqx '# Composio CLI' "$login_file" \
117
+ && grep -Fqx 'export PATH="$HOME/.local/bin:$PATH"' "$login_file"; then
118
+ echo "✅ $login_file gained the managed Composio PATH block via automatic shell setup"
119
+ else
120
+ echo "❌ $login_file missing the managed Composio PATH block after the no-argument install"
121
+ echo "=== $login_file contents ==="
122
+ cat "$login_file" || true
123
+ exit 1
124
+ fi
125
+
126
# Assert a login shell actually resolves the binary through that PATH block.
108
- if bash -ilc 'command -v composio' && bash -ilc 'composio --version'; then
127
+ # env -i drops the step's inherited PATH: GITHUB_PATH from the pinned-tag step
128
+ # and Ubuntu's skel ~/.profile both already prepend ~/.local/bin, so a probe
129
+ # that inherits them would pass even if the login-file write regressed. This
130
+ # mirrors the harness's assert_login_bash_path clean-environment probe.
131
+ if env -i HOME="$HOME" PATH=/usr/bin:/bin bash -ilc 'command -v composio' \
132
+ && env -i HOME="$HOME" PATH=/usr/bin:/bin bash -ilc 'composio --version'; then
133
echo "✅ composio resolves via a login bash shell"
134
else
135
echo "❌ composio did not resolve via a login bash shell"