Skip to content

meta(deps): Update retry-as-promised to 5.0.0#13785

Merged
sdepold merged 3 commits intosequelize:mainfrom
akre54:patch-1
Dec 21, 2021
Merged

meta(deps): Update retry-as-promised to 5.0.0#13785
sdepold merged 3 commits intosequelize:mainfrom
akre54:patch-1

Conversation

@akre54
Copy link
Copy Markdown
Contributor

@akre54 akre54 commented Dec 17, 2021

Pull Request Checklist

Please make sure to review and check all of these items:

  • Have you added new tests to prevent regressions?
  • Does npm run test or npm run test-DIALECT pass with this change (including linting)?
  • Is a documentation update included (if this change modifies existing APIs, or introduces new ones)?
  • Did you update the typescript typings accordingly (if applicable)?
  • Does the description below contain a link to an existing issue (Closes #[issue]) or a description of the issue you are solving?
  • Did you follow the commit message conventions explained in CONTRIBUTING.md?

Description Of Change

Earlier versions of retry-as-promised rely on the package any-promise which depends on a global window object. This change makes Sequelize a bit easier to use on node environments, especially with server side rendering like next.js

Earlier versions of retry-as-promised rely on any-promise which relies on a global `window` object. This change makes Sequelize a bit easier to use on node environments, especially with server side rendering like next.js
@sdepold sdepold merged commit 49fb726 into sequelize:main Dec 21, 2021
@github-actions
Copy link
Copy Markdown
Contributor

🎉 This PR is included in version 6.12.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

aliatsis pushed a commit to creditiq/sequelize that referenced this pull request Jun 2, 2022
Earlier versions of retry-as-promised rely on any-promise which relies on a global `window` object. This change makes Sequelize a bit easier to use on node environments, especially with server side rendering like next.js

Co-authored-by: Rik Smale <[email protected]>
Co-authored-by: Sascha Depold <[email protected]>
@depoulo
Copy link
Copy Markdown

depoulo commented Jul 5, 2022

Looking at the diff, I wonder whether you guys really didn't have to change anything regarding this breaking change: mickhansen/retry-as-promised#26

@depoulo
Copy link
Copy Markdown

depoulo commented Jul 5, 2022

Hm I see #13494

@WikiRik
Copy link
Copy Markdown
Member

WikiRik commented Jul 5, 2022

That breaking change is retry-as-promised v3 to v4. This PR is about v4 to v5; mickhansen/retry-as-promised@v4.0.0...v5.0.0 so we didn't have to change anything

@depoulo
Copy link
Copy Markdown

depoulo commented Jul 5, 2022

Yeah sorry I meant 3 to 4.

@depoulo
Copy link
Copy Markdown

depoulo commented Jul 5, 2022

Anyway, I don't see a related change in #13729 but I guess that's ok.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants