Why doesn't the MJML app use the latest version of MJML?

[torncheesecake]

As the title says, why doesn't the MJML app use the latest version of MJML? Currently my app is using 4.1.2, anything I do to try and point it to a custom engine doesn't work. But the app should really auto update to using the current latest version of MJML, much like browsers etc do and other programs do with updates like Atom.

[medarob]

That would be good! I wonder myself why the App is not up-to-date...

[vicmunez85]

Ditto, This would be amazing. I see releases with new features but no updates to the app :(

[ngarnier]

Indeed, the update of MJML version is not automatic so we have to do it manually: update the MJML version, do some potential updates based on the changes internal to MJML, build the app for each OS and release.

Feel free to contribute by proposing a way to automate this flow.

[torncheesecake]

Feel free to contribute by proposing a way to automate this flow.

I'm assuming because atom is a github program that it uses some checking script and pull to update the version. I've noticed that there is a github feature coming so maybe that might help the project.

[keberox]

Since the app is using Electron, I believe this should not be difficult to accomplish - having the app use the latest version of the MJML engine.

[kmcb777]

Hi @matthewahillman @medarob @vicmunez85 @keberox , a new app release is available with mjml4.3.1, feel free to try it out !