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 #108
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-49a75b99b56a564815039949a4bb2832
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
sequelizefrom v3 to v6 is a major change that introduces numerous breaking changes. The current codebase is incompatible with this new version and will break if this PR is merged as-is. A significant refactoring effort is required.Here are the critical issues that must be addressed:
1. Incompatible Dependencies:
connect-session-sequelize@3.0.0(line 28) is not compatible with Sequelize v6. It must be upgraded (e.g., to^7.1.2).sequelize-handlers@0.1.7(line 91) is an abandoned package that depends on Sequelize v3. It must be removed or replaced.2. Sequelize API Breaking Changes:
Sequelize.Promiseis removed: This will cause errors inseed.js:10andclearDb.js:7. Use native Promises instead.classMethodsandinstanceMethodsare removed: Thedb.defineoptions forclassMethodsandinstanceMethodswere removed in Sequelize v5. This will break all model definitions, for example inserver/db/models/Annotations/Annotation/index.js:19-20. These methods need to be refactored.$ne) are no longer supported by default. You must useSequelize.Opsymbols. This affects queries like the one inseed.js:256.user.createOrganization(seed.js:111) andteam.addStudent(seed.js:246) has changed..each()are no longer available on Sequelize promises (e.g.,seed.js:240). The code should be updated to use standard Promise patterns.