Skip to content

Conversation

@samsonasik
Copy link
Member

@samsonasik samsonasik commented Oct 20, 2025

@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,

@samsonasik
Copy link
Member Author

samsonasik commented Oct 20, 2025

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 samsonasik merged commit 60336a4 into main Oct 20, 2025
58 of 60 checks passed
@samsonasik samsonasik deleted the fix-e2e-test-invalid-paths branch October 20, 2025 13:44
@samsonasik samsonasik changed the title Update e2e/invalid-paths expected output on latest linux build Update e2e/invalid-paths expected output on latest webmozart/assert 2 build Oct 20, 2025
@samsonasik samsonasik changed the title Update e2e/invalid-paths expected output on latest webmozart/assert 2 build Update e2e/invalid-paths expected output on latest webmozart/assert 1.12 build Oct 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants