Bumping the major gem version as well when the major version of MRML is bumped #28
Description
Is your feature request related to a problem? Please describe.
The 1.8.0 release contained a major MRML version upgrade from 4 to 5. It isn't obvious from the release notes but MRML 5 contains at least one breaking change. mj-text is an "ending tag" meaning that it shouldn't contain other MJML components but MRML 4 still parses the nested components and 5 doesn't.
This caused an issue for us because we didn't expect breaking changes in a minor gem version update.
Describe the solution you'd like
I think that the major gem version should be bumped as well when the MRML major version is bumped to avoid surprises.