-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump pdfmake from 0.2.17 to 0.2.18 in /components #11485
base: dev
Are you sure you want to change the base?
Bump pdfmake from 0.2.17 to 0.2.18 in /components #11485
Conversation
Bumps [pdfmake](https://github.com/bpampuch/pdfmake) from 0.2.17 to 0.2.18. - [Release notes](https://github.com/bpampuch/pdfmake/releases) - [Changelog](https://github.com/bpampuch/pdfmake/blob/0.2.18/CHANGELOG.md) - [Commits](bpampuch/pdfmake@0.2.17...0.2.18) --- updated-dependencies: - dependency-name: pdfmake dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
DryRun Security SummaryThe pull request updates the versions of Expand for full summarySummary: The code changes in this pull request primarily involve updating the versions of the From an application security perspective, keeping dependencies up-to-date is generally a good practice, as it helps to mitigate potential security risks and improve the overall security posture of the application. However, it's important to thoroughly test the changes to ensure that the updated dependencies do not introduce any regressions or unexpected behavior in the application. Additionally, it's crucial to review the changelog or release notes of the updated dependencies to ensure that there are no known security vulnerabilities that have been addressed in the new versions. Maintaining an up-to-date inventory of dependencies, monitoring for security advisories, and conducting thorough testing are all important steps to take to ensure the ongoing security of the application. Files Changed:
Code AnalysisWe ran
|
DryRun Security SummaryThe pull request updates the versions of Expand for full summarySummary: The code changes in this pull request primarily involve updating the versions of the From an application security perspective, keeping dependencies up-to-date is generally a good practice, as it helps to mitigate potential security risks and improve the overall security posture of the application. However, it's important to thoroughly test the changes to ensure that the updated dependencies do not introduce any regressions or unexpected behavior in the application. Additionally, it's crucial to review the changelog or release notes of the updated dependencies to ensure that there are no known security vulnerabilities that have been addressed in the new versions. Maintaining an up-to-date inventory of dependencies, monitoring for security advisories, and conducting thorough testing are all important steps to take to ensure the ongoing security of the application. Files Changed:
Code AnalysisWe ran
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved
Bumps pdfmake from 0.2.17 to 0.2.18.
Release notes
Sourced from pdfmake's releases.
Changelog
Sourced from pdfmake's changelog.
Commits
a7b349a
0.2.18e8dbc24
Update pdfkitd2dd211
year++4c50979
update dependencies98558fd
fixed a potential issue in the minimized library when detecting the orientati...Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)