You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit cf21a9c
Browse filesBrowse the repository at this point in the historyBrowse files
fix(cli): let --secrets-file values win over remoteEnv in hooks
The reference runs every lifecycle hook with {...remoteEnv, ...secrets},
where remoteEnv is the probed env, then --remote-env, then the config's
remoteEnv. up and run-user-commands put the secrets before both remoteEnv
sources, so a remoteEnv entry of the same name hid the secret.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
notes: "Same precedence as up.secrets-override-remote-env-success: run-user-commands hands runLifecycleHooks the probed remoteEnv and the secrets, and each hook runs with {...remoteEnv, ...secrets}."
notes: "Lifecycle hooks see {...remoteEnv, ...secrets} (injectHeadless.ts runLifecycleCommand), where remoteEnv is the probed env, then --remote-env, then the config's remoteEnv (probeRemoteEnv): a --secrets-file value beats both remoteEnv sources of the same name, and the config's remoteEnv beats --remote-env. Go put the secrets before both, so remoteEnv won."
0 commit comments