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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Upgrade sequelize from 5.21.6 to 5.21.7 #5

Merged
merged 2 commits into from
Apr 27, 2020

Conversation

snyk-bot
Copy link
Contributor

Snyk has created this PR to upgrade sequelize from 5.21.6 to 5.21.7.

merge advice

鉁╓hat is Merge Advice? We check thousands of dependency upgrade pull requests and CI tests every day to see which upgrades were successfully merged. After crunching this data, we give a recommendation on how safe we think the change is for you to merge without causing issues. Learn more, and share your feedback to help improve this feature. 馃檹

鈩癸笍 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 1 version ahead of your current version.
  • The recommended version was released 3 days ago, on 2020-04-23.
Release notes
Package name: sequelize from sequelize GitHub release notes
Commit messages
Package name: sequelize
  • 028f656 fix(include): separate queries are not sub-queries (#12152)

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

@cslin82 cslin82 merged commit b5c5187 into master Apr 27, 2020
@cslin82 cslin82 deleted the snyk-upgrade-85576016657e5747cb7c8ff5c74002a4 branch April 27, 2020 17:58
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.

None yet

2 participants