Bug Report
Summary
conda build is unavailable in GitHub Actions despite conda-build being installed in a previous workflow step. The same recipe and workflow previously worked without modification and continues to build successfully in local environments.
Environment
- CI: GitHub Actions
- Conda setup:
setup-miniconda
- Affected command:
conda build
- Local environment: Works as expected
Steps to Reproduce
- Run GitHub Actions workflow that installs
conda-build
- Attempt to run
conda build <recipe>
- Observe command not found / unavailable error
Expected Behavior
conda build should be available after installing conda-build in CI, matching local behaviour.
Actual Behavior
conda build is not available in later workflow steps, despite successful installation earlier in the job.
Local Reproduction Status
- Builds successfully locally using identical recipe and command
- Issue is CI-specific and not reproducible outside GitHub Actions
Additional Context
This workflow previously worked without issue and no relevant changes were made to the workflow or recipe prior to the failure.
The root cause appears to be inconsistent Conda environment activation or shell state persistence between workflow steps in GitHub Actions.
Applying consistent environment activation (e.g. auto-activate: true and explicitly activating the target environment such as base) resolves the issue.
Bug Report
Summary
conda buildis unavailable in GitHub Actions despiteconda-buildbeing installed in a previous workflow step. The same recipe and workflow previously worked without modification and continues to build successfully in local environments.Environment
setup-minicondaconda buildSteps to Reproduce
conda-buildconda build <recipe>Expected Behavior
conda buildshould be available after installingconda-buildin CI, matching local behaviour.Actual Behavior
conda buildis not available in later workflow steps, despite successful installation earlier in the job.Local Reproduction Status
Additional Context
This workflow previously worked without issue and no relevant changes were made to the workflow or recipe prior to the failure.
The root cause appears to be inconsistent Conda environment activation or shell state persistence between workflow steps in GitHub Actions.
Applying consistent environment activation (e.g.
auto-activate: trueand explicitly activating the target environment such asbase) resolves the issue.