Good morning @Pintoch, I'm happy to have a look at fixing this - would you be able to add me to the repo?

Fantastic! I've added you to the org.

Update, encountered a different issue - pulling the previous credentials out was easy, but I am having trouble getting the gitlab runner to build anything due to communication issues with docker: https://gitlab.wikimedia.org/repos/wikibase-reconciliation/wikibase-reconciliation-wrapper/-/jobs/837388. I haven't worked with docker-in-docker on a kubernetes runner system before, so will investigate if I can route my way around it, or whether it depends on runner permissions, or switch to a completely different base image entirely.

Spent some time trying to fix by moving to podman for docker image build and test, but hitting permissions issues via that route as well - I think I'm hitting a wall on how much I can achieve without talking to someone if there are any precedents for doing with kind of thing in this environment, or whether I am able to tweak the runner permissions to my advantage. @Pintoch do you have any insight as to who would be the best person to throw this question to within Wikimedia?

I would ask for advice on IRC, #wikimedia-gitlab on libera.chat. I'm sure there are people there who could tell you if what you're trying to do can fit in the CI offering in this gitlab instance.
As a temporary measure to get things unblocked (since not having a working CI will prevent contributions from being reviewed), we could set up a basic CI which just runs the Python tests, without building a Docker image. I imagine it would remain useful even once the Docker issues are resolved, since building the Docker image probably doesn't run any tests anyway, so it would be complementary, no?

It seems we need to change the registry - https://www.mediawiki.org/wiki/GitLab/Workflows/CI

Can you try that one, in case you haven’t already?