feat: add support for publishing python packages to forgejo #13

Merged
cpressland merged 1 commit from feat/publish-python-packages-to-forgejo into main 2026-09-11 08:55:49 +01:00
Collaborator

Mirrors the same change made to whos-been in commit 5a48242604a05502385ce815b9e7c2623c149626:

  • Switches the CI workflow to use uv-buildah-build-push.yaml instead of buildah-build-push.yaml, which publishes the built Python package to the Forgejo PyPI registry before building the container image.
  • Simplifies the Containerfile to a slim python:3.14-slim base image that installs the published package via pip from the Forgejo PyPI index, instead of building from source with uv + distroless.
Mirrors the same change made to whos-been in commit 5a48242604a05502385ce815b9e7c2623c149626: - Switches the CI workflow to use `uv-buildah-build-push.yaml` instead of `buildah-build-push.yaml`, which publishes the built Python package to the Forgejo PyPI registry before building the container image. - Simplifies the Containerfile to a slim `python:3.14-slim` base image that installs the published package via `pip` from the Forgejo PyPI index, instead of building from source with uv + distroless.
Hermes force-pushed feat/publish-python-packages-to-forgejo from e42b0a187f to 0f20dcf9df
All checks were successful
ci / uv-buildah-build-push (push) Successful in 23s
ci / build (push) Successful in 0s
2026-09-11 08:55:28 +01:00
Compare
cpressland deleted branch feat/publish-python-packages-to-forgejo 2026-09-11 08:55:49 +01:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
cpressland/rabbitdb!13
No description provided.