[php] Update phpunit/phpunit 11.5.33 → 11.5.35 (patch) #212
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
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.
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ phpunit/phpunit (11.5.33 → 11.5.35) · Repo
Release Notes
11.5.35
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 41 commits:
Prepare releaseUpdate dependenciesPrevent unnecessary duplicate work in `DataProvider->providedData()`Configure separate result cache path per branchUpdate ChangeLogTest runner deprecation from subprocesstest method level metadataTest runner deprecations can be ignoredAdded regression test to prevent endless loop in subprocessReflect endless loop preventing fix in AnnotationParser->forMethod()Take #[IgnorePhpunitDeprecations] attribute into account for test runner deprecationsMerge branch '10.5' into 11.5Merge branch '9.6' into 10.5Merge branch '8.5' into 9.6Update toolsMerge branch '10.5' into 11.5Merge branch '9.6' into 10.5Merge branch '8.5' into 9.6Clean up after #6323Merge branch '10.5' into 11.5Merge branch '9.6' into 10.5Fix CS/WS issueMerge branch '10.5' into 11.5Merge branch '9.6' into 10.5Merge branch '8.5' into 9.6Fix test that was passing only when run sequentiallyMerge branch '10.5' into 11.5Merge branch '9.6' into 10.5Merge branch '8.5' into 9.6Added missing dependency to randomly failing testPrepare releaseMerge branch '10.5' into 11.5Prepare releaseMerge branch '9.6' into 10.5Prepare releaseMerge branch '8.5' into 9.6Prepare releaseMerge branch '10.5' into 11.5Merge branch '9.6' into 10.5Merge branch '8.5' into 9.6Do not set "report_memleaks" which will be deprecated in PHP 8.5Release Notes
11.0.11
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 9 commits:
Prepare releaseFix CS/WS issueConfigure separate result cache path per branchUpdate toolsSimplify applyFilter()invoke skipEmptyLines() even earlierImprove performance by skipping empty lines after filter has been appliedUpdate PHP-CS-Fixer configurationUpdate tools👉 No CI detected
You don't seem to have any Continuous Integration service set up!
Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.
This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:
* [Circle CI](https://circleci.com), [Semaphore ](https://semaphoreci.com) and [Github Actions](https://docs.github.com/actions) are all excellent options. * If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github. * If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with `depfu/`.Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands