Cache uv deps in deploy job and use uv pip install - #106
Merged
Conversation
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.
#98
CI/deploy hardening for repeated deploys:
deployjob: adds theactions/cacheon the uv cache (path now matches setup-uv'sUV_CACHE_DIR, shared key withsetup/lint/test) so deploys hit the shared wheel cache instead of re-downloading every time.deploy.sh:uv run pip install->uv pip installfor the Lambda vendoring (uv-native installer).deploy.yml: workflow-levelconcurrencygroup keyed on ref so overlapping runs serialize instead of double-deploying the same stack (previously causedResourceConflictException: An update is in progressonUpdateFunctionCodewhen two runs of the same commit deployed concurrently).deploy.sh:update_lambda_codenow captures and prints the real AWS error when a Lambda code update fails (was swallowed by&>/dev/null), so failures are diagnosable at a glance.Verified: all four
Cache uvsteps (setup/lint/test/deploy) restore at${{ runner.temp }}/setup-uv-cache, no more "cache path does not exist" warnings.