Skip to content
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

[Snyk] Upgrade jimp from 0.9.8 to 0.10.0 #29

Merged
merged 1 commit into from
Apr 1, 2020

Conversation

snyk-bot
Copy link
Contributor

@snyk-bot snyk-bot commented Apr 1, 2020

Snyk has created this PR to upgrade jimp from 0.9.8 to 0.10.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
  • The recommended version is 3 versions ahead of your current version.
  • The recommended version was released 2 days ago, on 2020-03-30.
Release notes
Package name: jimp
  • 0.10.0 - 2020-03-30

    🚀 Enhancement

    • @jimp/core, @jimp/custom, jimp, @jimp/jpeg

    Authors: 1

  • 0.9.9-canary.868.799.0 - 2020-03-30
  • 0.9.9-canary.867.792.0 - 2020-03-29
  • 0.9.8 - 2020-03-28

    🐛 Bug Fix

    • @jimp/plugins

    Authors: 1

from jimp GitHub release notes
Commit messages
Package name: jimp
  • c23237b Bump version to: v0.10.0 [skip ci]
  • 1add0ba Update CHANGELOG.md [skip ci]
  • e1d05da Properly split constructor and instance types (#867)

Compare


Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@huan huan merged commit 5d3bc1f into master Apr 1, 2020
@huan huan deleted the snyk-upgrade-6a0356e9682e154b93b0ce89f7dd55c1 branch November 14, 2020 17:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants