Update utopia-php/storage to 3.1 - #244
Merged
Merged
Conversation
Greptile SummaryUpdates
Confidence Score: 5/5The dependency-only update appears safe to merge, with no concrete compatibility, security, or lockfile consistency issue identified. The manifest and lockfile consistently select storage 3.1.0, retain the package’s existing dependency requirements, and make no executor source changes that introduce an observable failure. Important Files Changed
Reviews (1): Last reviewed commit: "Update utopia-php/storage to 3.1" | Re-trigger Greptile |
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.
What
Bumps
utopia-php/storagefrom 3.0.0 to 3.1.0. Composer updates only the storage package; there are no transitive dependency changes.Storage 3.0 was the major API migration handled in #243. Storage 3.1 keeps the APIs used by executor compatible and focuses on S3/Local reliability.
3.0 → 3.1
S3::exists()returnfalseonly for genuine not-found responses. Throttling, authentication, transport, and other remote failures now remain visible.Upstream comparison: utopia-php/storage@3.0.0...3.1.0
Executor impact
All remote backends created by
StorageFactory(S3, AWS, DigitalOcean Spaces, Backblaze, Linode, and Wasabi) use the S3 implementation, so the reliability improvements apply consistently across executor source downloads, build artifact uploads, and storage-backed build-cache transfers.No executor source changes are required because 3.1 does not break the storage APIs used here.
Verification
composer test:unit— 20 tests, 72 assertionscomposer analyze— no errorscomposer format:check— passedcomposer refactor:check— cleancomposer audit— no security advisoriesgit diff --check— cleanThe E2E suite requires the full Docker runtime stack and is left to CI.