fix(ios): Pin SnapshotPreviews#796
Merged
cameroncooke merged 1 commit intoApr 24, 2026
Merged
Conversation
Switch the SnapshotPreviews Swift package dependency from tracking the main branch to a semantic version range. Using a branch reference means every resolve can pull in unreviewed upstream changes, which makes builds non-reproducible and can break snapshot tests without warning. Pinning to a version range keeps updates explicit and reviewable while still allowing non-breaking upgrades below 1.0.0. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
📲 Install BuildsiOS
|
📸 Snapshot Test2 modified, 42 unchanged
🛸 Powered by Emerge Tools |
Sentry Snapshot Testing
|
f07a912 to
2cbe867
Compare
runningcode
approved these changes
Apr 24, 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.
Pin the
SnapshotPreviewsSwift package dependency to the semantic version range0.13.0..<1.0.0instead of tracking the upstreammainbranch.Tracking
mainmeant each resolve could pull in unreviewed upstream changes, making builds non-reproducible and leaving snapshot tests vulnerable to breakage from dependency drift. Pinning to a version range keeps future updates explicit and reviewable while still allowing non-breaking upgrades within the 0.x line.Resolved revision moves from
ee693c3(unversionedmain) to83131a5(tag0.13.0).