I know this comment is a lot of words, and may feel critical, but I assure you I mean them in the spirit of "for your consideration" and want to start off by saying thank you for sharing such a cool toy with the world under a permissive license. Great job, and thank you!

I was trying to find out which version of python it offered, and while digging into that I found surprising references to win32 binaries in the pyproject <https://github.com/Amourspirit/python_libre_pythonista_ext/b...> although the extensions page says it's for all 3 major OSes.

Related to that permalink, please do consider creating a formal tag that represents the code that went into the 0.1.1 binary you linked to. It'll greatly help those trying to track down bugs if they don't have to $(git bisect) in order to find out which sha created the extension they're using

Kind of related to that, future you (and folks who clone your repo) are going to be sad if you keep putting the release artifacts in git, since it will make your repo grow without bound. If you want to make the .oxt available to folks outside of the libreoffice.org URL, that's another fine reason to create a tag since GitHub will cheerfully hold on to the .oxt with a permalink forever, but outside of your repo. It'll also motivate you, or a contributor, to create a GitHub Action showing how normal people could possibly build the release artifact for themselves