chore: Change agbenchmark
to directory dependency in autogpt
and forge
#6946
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Poetry recently released a new version containing a fix for the issue we were having earlier:
python-poetry/poetry#8548
This means unavailable optional directory dependencies should no longer break the docker build.
Using directory dependencies has the advantage that we don't have to manually
chore: Update 'agbenchmark' dependency for agent and forge
(see commit history), because they'll always import the package directly from the folder in the local repo.Changes 🏗️
agbenchmark
dependency inforge/pyproject.toml
to a directory dependencypoetry.lock
agbenchmark
dependency inautogpt/pyproject.toml
to a directory dependencypoetry.lock
PR Quality Scorecard ✨
+2 pts
+5 pts
+5 pts
+5 pts
-4 pts
+4 pts
+5 pts
-5 pts
agbenchmark
to verify that these changes do not regress performance?+10 pts