v22 - Next Major Release #563
Description
We should discuss what we might want to do to start on a new major version of es-components. It doesn't have to be a huge change that we make to create the new version—I don't think we need to pack a lot into it, necessarily—but we should be conscious about creating a new major version since it will have significant downstream implications. (All teams using es-components will want to switch their Isolated Externals configurations to @22 instead of @21 so they can keep getting regular updates and bugfixes, and will need to make sure they're accommodating any breaking changes in their applications.)
It's also probably a good idea to strategize around ensuring that we only release breaking changes once. In that regard, we will want to include everything in the initial major version update that will cause breakages.
Some initial ideas that we could include in this initial major version release:
- Dropping support for styled-components@4
- Dropping support for React@16
We can also use this issue to talk about strategy for the development process in a new major version. Do we utilize a running next branch? Do we create a single PR that represents the initial major release? Etc.