Repository navigation
CI: Fix those pesky libretiny failures - #130
Merged
Merged
Conversation
The key rotates monthly so that unpinned platforms pick up new releases. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
mathieucarbou
approved these changes
Nov 1, 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.
Some platforms (such as LibreTiny) construct a Python venv in their package deployment, which gets baked in to the cache, and then breaks if the Python version is updated. Skip caching the deployments, and ensure caches have a limited lifetime so any other breakage doesn't persist indefinitely.