What churn are you referring to? I’m quoting directly from here: https://lit.dev/docs/v3/releases/upgrade/ https://lit.dev/docs/v3/releases/upgrade/ “For the

What churn are you referring to? I’m quoting directly from here: https://lit.dev/docs/v3/releases/upgrade/ https://lit.dev/docs/v3/releases/upgrade/ “For the *vast majority* of users there should be no required code changes to upgrade from Lit 2 to Lit 3. Most apps and libraries should be able to extend their npm version ranges to include both 2.x and 3.x, like "^2.7.0 || ^3.0.0".“ And here is v1 to v2 for completeness sake: https://lit.dev/docs/v2/releases/upgrade/ https://lit.dev/docs/v2/releases/upgrade/ Most of your examples are kind of odd. One of them was a brand change that involves no code at all. There is only one meaningful bit of churn in there which also was an overlay of the Web Platform itself. Polymer was a WebComponentsv0 library Lit is a WebComponentsv1 library.