-
Notifications
You must be signed in to change notification settings - Fork 286
Upgrade to Sequelize 6.1.1 #807
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
Conversation
Good job. Looks like it's mostly a subset of the changes from #787 - with some minor stylistic difference. Quickly comparing the two, I find a few files that I'd changed that you did not. Most likely the target moved: 6.0.0 beta 6 vs 6.2. Any thoughts? I'm still in crunch until the 15th or so, so I've only been pushing patches to projects that are causing active breakage in the code I'm working on - and I've not yet had the time to upgrade deps on the project past the 6 beta... If this PR is able to get things fixed I'm all for it! |
quick note, can the sequelize version be |
Everything looks fine and running without any problems. I almost read sequallize all changelogs releases by release. I tried to change minimum code to accommodate new the changes and pass all the tests. |
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.
looks good to me
Great work @Awais000! Getting this merged & released would be highly appreciated 👍 Does someone btw have knowledge on which versions of typescript are compatible? |
Hi, any update on when this will be merged and pushed to Npm? |
@RobinBuschmann can we get this merged in? |
@Awais000 Didn't noticed it in the first place. Why did you delete the package-lock.json? |
I've published a new version ( |
Have been using since you posted and everything is working until now. Thank you @Awais000 and everyone involved |
hi, just wondering whether this is supporting v6 now? As the readme on both github and NPM are stating for the support of Sequelize v5 |
Was this released? It is merged but it seems it isn't part of the latest release. |
hi @RobinBuschmann , any news on the release? |
Up |
The pull-request was merged but not released in npm yet. |
use |
am I right to assume that the sequelize-typescript v2 is only in beta and not fully release yet? |
…pescript Sequelize: 5.21.12 => 6.3.5 with breaking change release (https://github.com/sequelize/sequelize/releases/tag/v6.1.0) Sequelize-cli: 5.5.1 => 6.2.0 (https://github.com/sequelize/cli/releases/tag/v6.0.0 https://github.com/sequelize/cli/releases/tag/v6.1.0 https://github.com/sequelize/sequelize/releases/tag/v6.2.0) Sequelize-typescript: 1.1.0 => 2.0.0-beta.1 (sequelize/sequelize-typescript#807 and sequelize/sequelize-typescript#856)
[TECH] Upgrade sequelize, sequelize-cli and sequelize-typescript Upgrade details : - Sequelize: 5.21.12 => 6.3.5 with breaking change release (https://github.com/sequelize/sequelize/releases/tag/v6.1.0). Looking at the release note we are only impacted with one change from v6 (`addConstraint` method in migrations that now take only 2 parameters instead of 3). - Sequelize-cli: 5.5.1 => 6.2.0 (https://github.com/sequelize/cli/releases/tag/v6.0.0 https://github.com/sequelize/cli/releases/tag/v6.1.0 https://github.com/sequelize/sequelize/releases/tag/v6.2.0) - Sequelize-typescript: 1.1.0 => 2.0.0-beta.1 (sequelize/sequelize-typescript#807 and sequelize/sequelize-typescript#856 #8 See merge request appenin/falco-api!145
Upgraded to latest Sequlize which is at the moment v6.2
Executed and passed all the tests on every version after v5.22
Due to the depreciation of BlueBird, most of the breaking changes were in tests.
Other than that change in name of some function and typing compatibly.