coulomb/issue-core
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
issue-core/docs/package-release.md
tegwick 36ed581d89
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 2s
Details
Migrate issue-core OCI and PyPI refs to Forgejo (RAIL-HO-WP-0006)
2026-07-09 11:59:07 +02:00

1.1 KiB
Raw Blame History

Python Package Release

issue-core publishes as the issue-core Python package. The Railiance application deployment path expects the 0.2.x series to be available from the Coulomb Gitea PyPI registry.

Local Release

Build and validate the release artifacts:

make package-check

Publish to the Coulomb organization registry:

TWINE_USERNAME=<gitea-user> \
TWINE_PASSWORD=<package-token> \
make publish-gitea

The package endpoint is:

https://forgejo.coulomb.social/api/packages/coulomb/pypi

The matching simple index for consumers is:

https://forgejo.coulomb.social/api/packages/coulomb/pypi/simple/

Do not commit tokenized package index URLs. CI and local Docker builds should inject registry credentials through environment variables or BuildKit secrets.

Gitea Actions Release

The .gitea/workflows/publish-python-package.yml workflow publishes on tags matching v*. Configure these repository secrets before cutting a release:

  • GITEA_PACKAGE_USER
  • GITEA_PACKAGE_TOKEN

Release 0.2.0 with:

git tag v0.2.0
git push origin v0.2.0