Related to #1438, investigate if we can/should add a CI test job that installs icon4py "properly" in a sense that it would potentially catch if e.g. metadata is off (like in #1438 and the botched 0.4.0 release), without pushing a package to test.pypi.org. #1438 should already catch most causes of this, but the best test is if the packages actually install cleanly. I don't know if this is doable in a nice way.
Related to #1438, investigate if we can/should add a CI test job that installs icon4py "properly" in a sense that it would potentially catch if e.g. metadata is off (like in #1438 and the botched 0.4.0 release), without pushing a package to test.pypi.org. #1438 should already catch most causes of this, but the best test is if the packages actually install cleanly. I don't know if this is doable in a nice way.