fix: always run poetry install to prevent missing pytest from stale cache#27
Merged
LanusseMorais merged 1 commit intomainfrom Mar 26, 2026
Merged
Conversation
leandroh
approved these changes
Mar 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Command not found: pytestInstall dependenciesstep was conditional on cache miss, but the cached.venvwas stale (missing pytest)if: cache-hit != 'true'condition sopoetry installalways runspoetry installis a fast no-op (just verifies dependencies)Test plan
Note
Low Risk
Low risk CI-only change that may slightly increase job time but reduces flakiness from stale cached virtualenvs.
Overview
Integration test CI now always runs
poetry install --with deveven when the.venvcache is restored, preventing failures from stale caches missing dev tools likepytest.Written by Cursor Bugbot for commit dc2574d. This will update automatically on new commits. Configure here.