coulomb/issue-core
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: point package release canon at Forgejo PyPI
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 4s
Details

Browse source 
issue-core 0.2.1 is published on forgejo.coulomb.social; update release
docs and prefer publish-forgejo over legacy Gitea paths.
This commit is contained in:
tegwick 2026-07-12 01:02:38 +02:00
parent d030c20dff
commit 8305d27e4b
1 changed files with 8 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

16
docs/package-release.md
View file

@ -2,7 +2,7 @@
`issue-core` publishes as the `issue-core` Python package. The Railiance `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 application deployment path expects the `0.2.x` series to be available from the
Coulomb Gitea PyPI registry. Coulomb Forgejo PyPI registry (`forgejo.coulomb.social`).
## Local Release ## Local Release
@ -17,7 +17,7 @@ Publish to the Coulomb organization registry:
```bash ```bash
TWINE_USERNAME=<gitea-user> \ TWINE_USERNAME=<gitea-user> \
TWINE_PASSWORD=<package-token> \ TWINE_PASSWORD=<package-token> \
make publish-gitea make publish-forgejo
``` ```
The package endpoint is: The package endpoint is:
@ -35,15 +35,15 @@ https://forgejo.coulomb.social/api/packages/coulomb/pypi/simple/
Do not commit tokenized package index URLs. CI and local Docker builds should Do not commit tokenized package index URLs. CI and local Docker builds should
inject registry credentials through environment variables or BuildKit secrets. inject registry credentials through environment variables or BuildKit secrets.
## Gitea Actions Release ## Forgejo Actions Release
The `.gitea/workflows/publish-python-package.yml` workflow publishes on tags The `.forgejo/workflows/publish-python-package.yml` workflow publishes on tags
matching `v*`. Configure these repository secrets before cutting a release: matching `v*` or `workflow_dispatch`. Configure org secrets:
- `GITEA_PACKAGE_USER` - `FORGEJO_PYPI_USER`
- `GITEA_PACKAGE_TOKEN` - `FORGEJO_PYPI_TOKEN`
Release `0.2.0` with: Release with:
```bash ```bash
git tag v0.2.0 git tag v0.2.0