✅ Fix snapshot tests#547
Merged
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
1 participant
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.
Two transitive dep updates broke snapshot assertions on fresh CI installs (we don't commit a lockfile).
spatie/pest-plugin-snapshots2.3.1 (spatie/pest-plugin-snapshots#23) removed a double-increment of the snapshot ID counter, so suffixes now start at __1 instead of __2. Our committed snapshots used the old 2.3.0 numbering. Regenerated against 2.3.1 — content unchanged, only the numbering.symfony/yamlv8 dumps an empty inline array as{}where v7 used{ }. Since v8 requires PHP >=8.4, the 8.3 job resolved v7 and 8.4/8.5 resolved v8, so theenqueue_csssnapshot couldn't match across the matrix. Normalized empty inline collections in a customObjectDriverso both versions pass.