⬆️ Update spatie/pest-plugin-snapshots to ^2.3#497
Merged
Conversation
pest-plugin-snapshots 2.3.0 moves the snapshot counter increment into getSnapshotId(), but MatchesSnapshots::doSnapshotAssertion() also increments it, causing a double-increment on each assertion. This shifts all snapshot IDs from __N to __2N. Updates the version constraint and renames all snapshot files accordingly. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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.
Summary
spatie/pest-plugin-snapshotsconstraint from^2.1to^2.3__Nto__2Nto match new counter behaviorBackground
pest-plugin-snapshots 2.3.0introduced a double-increment bug: the snapshot counter is now incremented in bothMatchesSnapshots::doSnapshotAssertion()(existing) and the newSnapshotIdAware::getSnapshotId()override (new in 2.3.0). This shifts every snapshot ID from__Nto__2N.Since
composer.lockisn't committed, CI resolved2.3.0on the latest push and the tests started failing.🤖 Generated with Claude Code