CC: @aneesh-joseph

@potiuk would this run on every master PR? Seems like it might make sense on pushes to 1-10-test but not on master.

@potiuk would this run on every master PR? Seems like it might make sense on pushes to 1-10-test but not on master.

It also makes sense on master. I think we are going to release a chart from master that also works for latest released 1.10 version.. Ideally we should be able to release the helm chart from master (say with calver 2020.10.05 version that works nicely also for 1.10.11 image :).

We already rin similar tests for backport packages for example - we take the latest released airflow and we test if all the 'latest' backport packages can be installed with it.

Ahh ok I see where you're coming from. Since this isn't taking in any code changes and is instead just running against the most recent release... Though that raises the question: Are there any situations that would work for the NEXT release but not the current one? Though I guess that's a bridge we can cross if we get there.

Ahh ok I see where you're coming from. Since this isn't taking in any code changes and is instead just running against the most recent release... Though that raises the question: Are there any situations that would work for the NEXT release but not the current one? Though I guess that's a bridge we can cross if we get there.

I think it should never be the case. We have the rule (which I think we even written down in README) that whenever we introduce a breaking change in what we release, we do deprecation first and make it backwards compatible as a rule.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.