I have some major refactoring I want to do first, but the plan is to eventually publish it to crates.io

Awesome. Maybe we can share some modules in the future. I am currently working on the Wikibase API (https://crates.io/crates/wikibase) and it would be cool if both libraries would work together well.

It should be trivial to have a CI workflow that automatically publishes to crates.io whenever a new version is published; perhaps we should go this route. I can draft a PR which would do this.

It should be trivial to have a CI workflow that automatically publishes to crates.io whenever a new version is published

Publishing a new version when a new version is published? Huh?

And if you're suggesting to publish a new version with every push to master, no, denied.

The main issue is that we need to come up with a crate name since mediawiki is already taken.

And if you're suggesting to publish a new version with every push to master, no, denied.

Do you think I'm insane? The workflow would be triggered when a new Git tag is pushed to the repository (or whenever you push a button).

The main issue is that we need to come up with a crate name since mediawiki is already taken.

mediawiki-api doesn't appear to be taken, but we might want to include a note at the bottom of the README that indicates that mediawiki is a separate project.

Do you think I'm insane? The workflow would be triggered when a new Git tag is pushed to the repository (or whenever you push a button).

If I already have to create a git tag and update the version number in Cargo.toml manually and all the CI workflow does is run cargo publish for me? That doesn't seem worth it.