Warn possible multiversion compatibility problem
When making an update or change to the GraphQL API, the exiting, updated or new frontend components must remain backwards-compatible because we gradually rollout changes (the implication is that some Rails hosts might be running the previous version.)
The rule might not be familiar to the team or contributors who don't often make such user-facing changes and it is easy to miss it altogether during a review as was the case in !114848 (merged).
We should leverage the Danger tooling to warn if a MR might cause the multiversion compatibility problem when the following conditions are both met:
- Frontend assets are updated or created (
(ee|jh)app/assets/.js|.vue|.graphql
) - Backend GraphQL code are updated or created (
(ee|jh)/app/graphql
)
Edited by euko