Skip to content
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

Add migration from v10 to v11 #1893

Open
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

remy727
Copy link

@remy727 remy727 commented Dec 18, 2024

WHY are these changes introduced?

We don't have guide for migration from v10 to `v11

WHAT is this pull request doing?

Add migration from v10 to v11

Type of change

  • Patch: Bug (non-breaking change which fixes an issue)
  • Minor: New feature (non-breaking change which adds functionality)
  • Major: Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

  • I have used pnpm changeset to create a draft changelog entry (do NOT update the CHANGELOG.md files manually)
  • I have added/updated tests for this change
  • I have documented new APIs/updated the documentation for modified APIs (for public APIs)

@remy727 remy727 requested a review from a team as a code owner December 18, 2024 19:21
Copy link
Contributor

@lizkenyon lizkenyon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi

For the migration guide we generally only share the breaking changes, ie. the changes that a developer is required to make to update their library to this version.

For migrating to version 11 the only required change is to use a Node version greater than 16.

For further details about each release developers can see the release page.

@remy727
Copy link
Author

remy727 commented Dec 18, 2024

Gotcha. Updated the guide.


This document covers the changes apps will need to make to be able to upgrade to v11 of this package.

The main reason for this release was to remove support for Node 16 so we can continue to evolve this package, but we also took this opportunity to remove some deprecated features.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
The main reason for this release was to remove support for Node 16 so we can continue to evolve this package, but we also took this opportunity to remove some deprecated features.
The main reason for this release was to remove support for Node 16 so we can continue to evolve this package.

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

Successfully merging this pull request may close these issues.

2 participants