[core] Introduce canary releases

[oliviertassinari]

Summary

I couldn't find issues about this so opened one.

Whitenessing the latest mess that happen between Next.js and Material UI e.g. vercel/next.js#64518 integration makes it clear to me that without Next.js releasing a canary version daily, it would have been much harder to solve the problems, e.g. vercel/next.js#64518 (comment).

I connect this with Material UI, where it seems we need Base UI to release daily and Material UI to run its CI on that Base UI canny release daily, so we can spot issues before they are in stable releases (what we missed between Next.js and Material UI).

This won't truly solve the cases where fixing something in Material UI requires to coordinate some change in Base UI and some change in Material UI but maybe it coud be good enough.

Examples

No response

Motivation

No response

Search keywords: -

[michaldudak]

Material UI doesn't use @base_ui/react yet, so releasing canary versions today won't make a difference.
Once it does, we can adopt a strategy similar to infra tools: release after each merged PR.

[oliviertassinari]

👍 This issue main purpose is to have a place to discuss the solution. It feels like we won't be able to avoid solving it (at one point).