We should have pygfx@main and latest pygfx on pypi in our CI matrix. But if the job using pygfx from pypi fails we want it to produce some sort of "warning" instead of failing the entire action. Maybe we can do burningmantech/ranger-ims-server#1347
This will be useful for us to better automate releases, we will know whether our current main branch works with the latest pygfx before releasing without us trying them locally in a new env which is what we do now.
@clewis7 can you take a look and see if there are better ways to do this?
I think this is the last main thing we should do before the next release!
We should have
pygfx@mainand latestpygfxon pypi in our CI matrix. But if the job usingpygfxfrom pypi fails we want it to produce some sort of "warning" instead of failing the entire action. Maybe we can do burningmantech/ranger-ims-server#1347This will be useful for us to better automate releases, we will know whether our current main branch works with the latest
pygfxbefore releasing without us trying them locally in a new env which is what we do now.@clewis7 can you take a look and see if there are better ways to do this?
I think this is the last main thing we should do before the next release!