Use Forgejo package registry instead of standalone pypiserver #12

Merged
shuber merged 1 commit from feat/forgejo-package-registry into main 2026-09-07 09:42:35 +00:00
Owner

tanss-api + ninja-api now resolve from the Forgejo-native package registry. Standalone pypiserver (10.98.10.23:3009) no longer needed for builds.

tanss-api + ninja-api now resolve from the Forgejo-native package registry. Standalone pypiserver (10.98.10.23:3009) no longer needed for builds.
Use Forgejo package registry instead of standalone pypiserver
All checks were successful
Build and publish container / build-and-push (pull_request) Successful in 2m6s
0849bf8821
tanss-api and ninja-api now resolve from the Forgejo-native package
registry (git.datajob.de/api/packages/shuber/pypi). The standalone
pypiserver on 10.98.10.23:3009 is no longer needed for builds.
shuber merged commit ae7fda0664 into main 2026-09-07 09:42:35 +00: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
GENERAL/syncninja!12
No description provided.