1 of 1 people found this helpful
There will be model changes, but I'm not sure whether they will impact you. We will be adding support for transaction policy, which will add model classes and interfaces, but should not require a schema change. David is working on refactoring the composer/decomposer support to apply to all components, which *will* impact the schema and will introduce additional model classes. If you are not using either of these two things, then I don't think it will impact you. Off the top of my head, I can't think of any other changes.
Best thing to do here is have an example of the generated code in one of our tests. This way, we know if a config change breaks your generated project stuff or not. I think you are working on integrating some quickstarts into the release build - perhaps that would be sufficient? If not, then adding another test would probably be wise.
Sounds like it will be fine, as I won't be impacted by the changes you mentioned.
I have pull requests on the quickstarts and release repos, and those tests should be sufficient to pick up any issues.