thanks @afuetterer , looks fine to with the -slim image.
Am not sure whether we can also take this already in the 2.4.5 patch release? @jochenklar

Yes, and I think we should even do this directly from the GitHub actions to PyPI. I think a less prominent release is better for this. I will prepare a PR and then you can check if I did it right.

Yes, and I think we should even do this directly from the GitHub actions to PyPI. I think a less prominent release is better for this. I will prepare a PR and then you can check if I did it right.

this is just about the tpye of Ubuntu Image that the runner uses, we can also try this in the 2.4.5 right?

Yes, and I think we should even do this directly from the GitHub actions to PyPI. I think a less prominent release is better for this. I will prepare a PR and then you can check if I did it right.

this is just about the tpye of Ubuntu Image that the runner uses, we can also try this in the 2.4.5 right?

That is correct.

Ive change it but now there is this merge conflict on the changelog. Can I force push to this branch (is that ok) or should we cherry pick the commit simply on a new branch from the 2.4.5/release and make a new PR? Or do you want to rebase and force push it?

Please do. My changes are in ci.yml only.

Coverage is 94.901% — afuetterer:ci into rdmorganiser:2.4.5/release. No base build found for rdmorganiser:2.4.5/release.

A slimmer VM and tests still run on same speed!

But less compute ressources are used. I think its better to just take what you need. Poor GitHub is struggling these days.

I don't think that it is us taking so many resources when they are building "Copilots" in all of their products 😅 but yeah fair use seems also better to me

Agreed.

Merge then?