forked from jes708/CodeGenius
-
Notifications
You must be signed in to change notification settings - Fork 0
[Snyk] Security upgrade sequelize from 3.35.1 to 6.6.5 #106
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
Open
saurabharch
wants to merge
1
commit into
master
Choose a base branch
from
snyk-fix-b626d559cea636823f5dad9782b53035
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
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.
Upgrading Sequelize directly from v3.x to v6.x introduces significant breaking changes that will cause the application to fail. The codebase uses several patterns and APIs that were removed in versions 4 and 5.
Here are the main issues that need to be addressed:
connect-session-sequelize(currently^3.0.0) needs to be upgraded to a version compatible with Sequelize v6 (likely v7+).sequelize-handlers(currently^0.1.7) appears to be unmaintained and is incompatible. It will need to be replaced or removed.Sequelize.Promise:seed.jsandclearDb.jsuserequire('sequelize').Promise, which was removed in Sequelize v4. You should switch to nativePromiseor another promise library likebluebird(which is already a dependency).classMethodsandinstanceMethods, which were removed in Sequelize v5. These models need to be refactored.seed.jsuses string-based operators (e.g.,$ne). These are deprecated and disabled by default in v5+. They must be replaced with symbol-based operators (e.g.,[Op.ne]).Given the extent of the required changes, I recommend treating this upgrade as a larger refactoring task rather than a simple dependency bump.