Jan Potoms

@nathanjisaac I don't think it should be solved by the linter. This is a mocha specific option and I only want it when I run my tests in a CI...

I still think it makes sense in the context of this library. But I've moved on to a webpack+mocha approach that makes more sense to me. So I'm not actively...

ever thought about using [htmlparser2](https://www.npmjs.com/package/htmlparser2)?

We would still be doing the exact workflow under the hood. The only **real** functionality we'd be taking away here is the ability to roll back releases. If we want...

> What do you think about the solution Jan proposed. We'll show the Releases tab in inactive state. On hover, it will show "Only available in paid plan". I didn't...

> So I was thinking that if we are looking into putting this feature behind paid plan then maybe instead "free" Toolpad version by default should only allow to have...

> An app could still be usable. Just that the developer will have to convey to the end user that "I am updating the app, I'll let you know once...

> it really depends how we want to price things That should definitely be a big factor, but Toolpad is also an open source project, which means that we also...

> pipedream.com doesn't have versioning Their deployments feature looks pretty close to me to how we do releases with Toolpad. Main differences: * pipedream deployments are snapshots of the application,...

I proposed an alternative as a separate RFC (https://github.com/mui/mui-toolpad/issues/868), but can add it as a comment here instead if that makes more sense?