Repository navigation
v0.3.0
Fixes multiple issues with how repos are setup to ensure all of their dependencies are installed and all databases seeded before running tests or handing the repo to an agent to work on. Added a way to save repo setup results separate from test results, so pipelines can handle when the setup fails and tests can't run.
Also fixed a bug with resolving values set to a non-None falsey value.
Summary
Enhancements
- Introduced
setup_propertyparameter to store setup results separately from test results inrun_unit_tests. - Added
skip_repo_setupparameter torun_swe_agentto prevent the setup scripts from running before handing the repo to the agent. Useful when asking the agent to analyze the raw repo.
Bug Fixes
- Breaking: Corrected resolution of falsey non-None values ("", [], 0, False) when using the
set_item_propertyaction. Previously they resolved toNone; now they resolve to the value provided - Fixed duplicated and inconsistent repo setup behavior where repos were sometimes being set up twice during tests (if requirements.txt existed) and not at all during agent runs.
- Ensured Python packages can install without a virtual machine by setting
PIP_BREAK_SYSTEM_PACKAGES - Updated Codex installation to use the correct Homebrew cask location.
- Reduced noise and improved speed by setting HOMEBREW_NO_AUTO_UPDATE=1.
- Fixed import in example pipeline.
Components
Updated
Item Actions
run_swe_agent
: Added skip_repo_setup parameter to allow conditional repository initialization.
run_unit_tests
: Added setup_property parameter to specify which item property to save the setup results to.