Skip to content

Conversation

@schlessera
Copy link
Member

@schlessera schlessera commented May 6, 2025

@schlessera schlessera requested a review from a team as a code owner May 6, 2025 09:01
@schlessera schlessera added this to the 2.12.0 milestone May 6, 2025
@schlessera schlessera force-pushed the fix/phar-path-resolution branch from 23832ee to 3e76f57 Compare May 6, 2025 09:11
@schlessera schlessera force-pushed the fix/phar-path-resolution branch 2 times, most recently from 2993729 to b9c5d01 Compare May 6, 2025 09:28
@schlessera schlessera force-pushed the fix/phar-path-resolution branch from b9c5d01 to 806b93e Compare May 6, 2025 09:34
@schlessera
Copy link
Member Author

Okay, we now have a test that makes the Phar resolution issue reproducible. Now I'll try my hand at a fix... :)

@schlessera schlessera changed the title Add tests to trigger phar path resolution bug Fix phar path resolution with renamed binaries May 6, 2025
@schlessera schlessera added the bug Something isn't working label May 6, 2025
@schlessera
Copy link
Member Author

Test failure seems only related to coverage, ignoring for now.

@schlessera schlessera merged commit e95fd10 into main May 6, 2025
42 of 43 checks passed
@schlessera schlessera deleted the fix/phar-path-resolution branch May 6, 2025 10:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

wp theme status <theme-name> throws: Error: Couldn't find theme-status.mustache

3 participants