🚨 [security] Update mpdf/mpdf 7.1.4 → 7.1.9 (patch) #3
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.
Welcome to Depfu 👋
This is one of the first three pull requests with dependency updates we've sent your way. We tried to start with a few easy patch-level updates. Hopefully your tests will pass and you can merge this pull request without too much risk. This should give you an idea how Depfu works in general.
After you merge your first pull request, we'll send you a few more. We'll never open more than seven PRs at the same time so you're not getting overwhelmed with updates.
Let us know if you have any questions. Thanks so much for giving Depfu a try!
🚨 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?
✳️ mpdf/mpdf (7.1.4 → 7.1.9) · Repo · Changelog
Security Advisories 🚨
🚨 mPDF Unsafe Deserialization
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Commits
See the full diff on Github. The new version differs by 52 commits:
Merge pull request #175 from fsevestre/173-chainable-filter
Allow applying further filters with ChainableFilter
Merge pull request #171 from Slamdunk/enum
Remove redundant check
Merge branch 'enum' of github.com:Slamdunk/DeepCopy into enum
Backward compatibility
Merge branch '1.x' into enum
Merge pull request #172 from Slamdunk/build_fix
enum_exists may have been manually declared on lower PHP versions, use strict PHP version check
Keep PHP 8.1 enums as is
Explicit package version to tackle circular ref with phpunit
Add CI badge
Add support for doctrine/common v3
Raise minimum required version to pass --prefer-lowest build
Disable code coverage
Improve README
Fix code example
Merge pull request #170 from Slamdunk/github_actions
Adapt test to new tools
Remove composer invalid entries
composer-normalize
Move from Travis to Github Actions
Merge pull request #169 from fridzema/patch-1
Tiny typo
Merge pull request #161 from youwe-petervanderwal/fix/unitialized-property-type-matcher
Add isInitialized check on PropertyTypeMatcher for PHP 7.4
Merge pull request #160 from villfa/patch-1
Fix Travis warning
Merge pull request #159 from open-source-contributions/test_enhancement_stuffs
Fix namespace and improve assertEquals
Fix copying objects extending ArrayObject (#152) (#155)
Fix copying objects extending ArrayObject (#152) (#155)
Allow PHP 8 (#157)
Exclude docs from being exported #151
Fix deep copying of ArrayObject in PHP 7.4 (#145)
Merge pull request #144 from SlvrEagle23/php74_compat
Fix "requires" annotation name.
Add PHP 7.4 as a testing target for Travis.
Add test entries for PHP 7.4 typed properties.
Fix minor typo.
Move check below setAccessible as it's necessary for private properties.
Add isInitialized check for PHP 7.4 typed properties.
Add link to Tidelift in README
Add strict types in tests
Move file into .github/ subfolder
Merge pull request #137 from myclabs/mnapoli-patch-1
Create FUNDING.yml
Merge branch '1.x' into mnapoli-patch-1
Run tests on PHP 7.3
Restore 1.x as the recommended version
Backport changes to gitattributes (#136)
Add filter prepend method (#132)
Release Notes
1.1.4
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 35 commits:
Merge pull request #74 from Jeckerson/master
Make type of 2nd argument `context` compliant with LoggerInterface
Revert "Clarify type of 2nd argument `context`"
Clarify type of 2nd argument `context`
Merge pull request #73 from varfrog/patch-1
Fix the phpdoc of LoggerAwareTrait::$logger
Merge pull request #71 from J0WI/patch-1
Update url to HTTPS
Merge pull request #70 from greg0ire/better-typehints
Be explicit about mixed context elements
Use PSR-4 for all classes (#69)
Create .gitattributes (#67)
Add "exception"-context array key to docs
Merge pull request #66 from WyriHaximus-labs/extract-DummyTest-into-its-own-file-and-return-empty-string-from-___toString
Return string from DummyTest::__toString
Merge pull request #55 from DQNEO/namespaced-phpunit
Remove alias as PHPUnit 4.8.35+ ships with it which is supporting PHP 5.3
Merge pull request #63 from ArturGoldyn/patch-1
Merge pull request #51 from Fleshgrinder/throws-annoation
Remove redundant leading backslashes
Update TestLogger.php
Merge pull request #58 from lyrixx/patch-1
Bump version to `1.1.x-dev`
Merge pull request #57 from gmponos/patch-2
Merge pull request #54 from RGustBardon/master
Create a new TestLogger
make alias from old one
make alias when new class does not exist
Merge pull request #53 from freekmurze/patch-1
fix white space
avoid side effect
use namespaced PHPUnit and keep B.C.
Test if the context array accepts closed resources
Make it a little bit easier to install this package
Added throws annoation to log methods
👉 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