Due to the recent issues where it was forgotten to update some code related to the ALWAYS_PREMIUMcompilation condition in #323, I thought it might make sense to also run the build & test steps for the Premium version as well.
This would allow us to catch compilation issues related the premium version earlier.
Also those jobs run in parallel so the additional overhead should be minimal.
Due to the recent issues where it was forgotten to update some code related to the
ALWAYS_PREMIUM
compilation condition in #323, I thought it might make sense to also run the build & test steps for the Premium version as well. This would allow us to catch compilation issues related the premium version earlier. Also those jobs run in parallel so the additional overhead should be minimal.