Skip to content

Conversation

@wolfy1339
Copy link
Member

This way we are certain that when updating people get the fixed versions of the modules

Should resolve #2439


Behavior

Before the change?

  • Plugins were locked to to a major version only, and users could get an older version of dependencies that had a bad release

After the change?

  • Bumps the dependencies to fixed versions so that users get fresh versions when they upgrade this package

Other information


Additional info

Pull request checklist

  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been reviewed and added / updated if needed (for bug fixes / features)
  • Added the appropriate label for the given change

Does this introduce a breaking change?

Please see our docs on breaking changes to help!

  • Yes (Please add the Type: Breaking change label)
  • No

If Yes, what's the impact:

  • N/A

Pull request type

Please add the corresponding label for change this PR introduces:

  • Bugfix: Type: Bug
  • Dependencies/code cleanup: Type: Maintenance

This way we are certain that when updating people get the fixed versions of the modules
@wolfy1339 wolfy1339 added the Type: Maintenance Any dependency, housekeeping, and clean up Issue or PR label May 19, 2023
@wolfy1339 wolfy1339 merged commit 3562907 into main May 19, 2023
@wolfy1339 wolfy1339 deleted the update-dependencies branch May 19, 2023 10:01
@github-actions
Copy link

🎉 This PR is included in version 2.0.16 🎉

The release is available on:

Your semantic-release bot 📦🚀

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

Labels

released Type: Maintenance Any dependency, housekeeping, and clean up Issue or PR

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

[BUG]: Typescript error on paginate string input

4 participants