v5.0.0-alpha.35

[oliviertassinari]

No description provided.

[mui-pr-bot]

No bundle size changes (experimental)

Generated by 🚫 dangerJS against 503d653

[siriwatknp]

should it be increment by 1 => 5.0.0-alpha.34?

I have no strong opinion here since it is still in alpha, but I lean toward whatever lerna version gave us. Last time that I did the release, I feel like there will be some error prone if we make the change manually.

If we want the version to be the same, then we should use independent: false

[oliviertassinari]

The above version was expected.

We have configured lerna version for the version to be independent because what "framer" needed was unclear. But the target is:

diff --git a/lerna.json b/lerna.json
index 06cff9cd69..8a385eae09 100644
--- a/lerna.json
+++ b/lerna.json
@@ -1,5 +1,5 @@
 {
   "npmClient": "yarn",
   "useWorkspaces": true,
-  "version": "independent"
+  "version": "5.0.0-alpha.35"
 }

I think that we should aim for the version to be as close as possible, at least, when in the same "realm". This makes it easier for the developers to manage versions. 1. At a glance at the package.json/yarn.lock you know if the versions are compatible. 2. Our approach to versioning in the documentation heavily depends on having a single version. 3. It's easier to communicate about the version of the product you are using (for us with announcements, between practitioners, etc.)

[eps1lon]

Did the explicit styleProps change land? If so, then we should document it as a breaking change.

[mnajdova]

Did the explicit styleProps change land? If so, then we should document it as a breaking change.

Not yet, I think I was waiting for review and then forgot about that PR will merge it tomorrow morning. I am merging the PR for adding createStyled in system tough @oliviertassinari FYI

styleProps is not yet merged: #26461