🚨 [security] [php] Update symfony/var-dumper 6.4.3 → 6.4.15 (patch) #109
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.
🚨 Your current dependencies have known security vulnerabilities 🚨
This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!
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?
Security Advisories 🚨
🚨 Symfony's VarDumper vulnerable to unsafe deserialization
Release Notes
6.4.15
6.4.4
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 50 commits:
Merge branch '5.4' into 6.4
relax format assertions for fstat() results on Windows
Merge branch '5.4' into 6.4
fix detecting anonymous exception classes on Windows and PHP 7
Merge branch '5.4' into 6.4
Add PR template and auto-close PR on subtree split repositories
Merge branch '5.4' into 6.4
[VarDumper] Fix tests
Merge branch '5.4' into 6.4
fix compatibility with Twig 3.12
Merge branch '5.4' into 6.4
[PhpUnitBridge][Console][VarDumper] Fix handling NO_COLOR env var
Merge branch '5.4' into 6.4
[VarDumper] Fix generator dump format for PHP 8.4
Merge branch '5.4' into 6.4
bug #57815 [Console][PhpUnitBridge][VarDumper] Fix `NO_COLOR` empty value handling (alexandre-daubois)
[Console][PhpUnitBridge][VarDumper] Fix `NO_COLOR` empty value handling
[ErrorHandler][VarDumper] Remove PHP 8.4 deprecations
[VarDumper] Fix `FFICaster` test to be platform-adaptable
[VarDumper] Fix FFI caster test
Merge branch '5.4' into 6.4
Revert "minor #54653 Auto-close PRs on subtree-splits (nicolas-grekas)"
fix tests
Merge branch '5.4' into 6.4
[VarDumper] Fix generator dump on PHP 8.4
Merge branch '5.4' into 6.4
[VarExporter] fix proxy helper when a method returns null
Remove calls to `TestCase::iniSet()` and calls to deprecated methods of `MockBuilder`
Merge branch '5.4' into 6.4
Auto-close PRs on subtree-splits
Merge branch '5.4' into 6.4
Adjust pretty name of closures on PHP 8.4
Merge branch '5.4' into 6.4
Make more nullable types explicit
Add more explicit nullable types for default null values
Merge branch '5.4' into 6.4
[VarDumper] Fix test suite with PHP 8.4
Merge branch '5.4' into 6.4
[TwigBridge] Fix compat with Twig v3.9
[VarDumper] Fix serialization of stubs with null or uninitialized values
fix test
bug #53842 [VarDumper] Fix configuring CliDumper with SYMFONY_IDE env var (nicolas-grekas)
[VarDumper] Fix configuring CliDumper with SYMFONY_IDE env var
Merge branch '5.4' into 6.4
[PhpUnitBridge][VarDumper] fix color detection
Merge branch '5.4' into 6.4
minor #53794 [PhpUnitBridge][VarDumper] Fix color detection (nicolas-grekas)
Skip Twig v3.9-dev for now
[VarDumper][PhpUnitBridge] Fix color detection
fix DoctrineCaster tests
👉 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