Skip to content

Update dependency @types/sequelize to v6 #128

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
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 4, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@​types/sequelize ^4.28.20 -> ^6.0.0 age adoption passing confidence

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/sequelize-6.x branch from 6c2cc73 to 5716cdb Compare August 5, 2025 18:36
@renovate renovate bot changed the title chore(deps): update dependency @types/sequelize to v6 Update dependency @types/sequelize to v6 Aug 5, 2025
@renovate renovate bot changed the title Update dependency @types/sequelize to v6 chore(deps): update dependency @types/sequelize to v6 Aug 7, 2025
@renovate renovate bot force-pushed the renovate/sequelize-6.x branch from 5716cdb to 4957e7f Compare August 7, 2025 23:35
@renovate renovate bot changed the title chore(deps): update dependency @types/sequelize to v6 Update dependency @types/sequelize to v6 Aug 12, 2025
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.

0 participants