Update e2e/invalid-paths expected output on latest webmozart/assert 1.12 build#7518
Merged
Conversation
Member
Author
|
I see, this is due to new webmozart/assert 1.12 https://github.com/webmozarts/assert/releases/tag/1.12.0 fixed with update message |
samsonasik
changed the title
samsonasik
changed the title
Contributor
|
This pull request has been automatically locked because it has been closed for 150 days. Please open a new PR if you want to continue the work. |
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
@TomasVotruba per latest PR build
https://github.com/rectorphp/rector-src/actions/runs/18652768149/job/53177257999?pr=7517#step:8:14
seems e2e/invalid-paths got different output, this PR fix it,