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 sequelize from 5.21.2 to 5.21.7 #176

Merged
merged 2 commits into from
May 25, 2020

Conversation

snyk-bot
Copy link
Contributor

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

ℹ️ 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 5 versions 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)
  • a2c0a63 fix(typings): support Date as where value (#12015)
  • 778819f fix(connection-manager): add switch for dynamic import (#12014)
  • 20e99e1 fix(model.count): distinct without any column generates invalid SQL (#11893)
  • 54d655d fix(typings): plain option in sequelize.query (#11929)
  • 43a8d61 fix(types): allow augmentation on model properties (#11882)
  • 81c33d8 fix(model): generate ON CONFLICT ... DO UPDATE correctly (#11666) (#11744)

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

@LukasLohoff LukasLohoff merged commit 8a48737 into master May 25, 2020
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