This repository has been archived by the owner on May 26, 2023. It is now read-only.
🚨 [security] Update symfony/http-kernel: 4.4.47 → 4.4.50 (patch) #4
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 storing cookie headers in HttpCache
Release Notes
4.4.50
4.4.49
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 2 commits:
Prepare for v1.27
CS fix
Commits
See the full diff on Github. The new version differs by 1 commit:
Prepare for v1.27
Commits
See the full diff on Github. The new version differs by 5 commits:
[VarDumper] Fix JS to expand / collapse
Bump license year to 2023
Use static methods inside data providers
Fix getting the name of closures on PHP 8.1.11+
[VarDumper] Ignore \Error in __debugInfo()
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