build: release on GitHub, crudylabs/pgmorbac and pgmorbac.crudy.fr

The signed distribution is published as a GitHub release by the release
workflow on v* tags, replacing the Gitea release and its Drone pipeline.
The release body and the dist README take the homepage from META.json.
This commit is contained in:
2026-10-03 15:32:06 +02:00
parent 1546e272d8
commit 3e8380d4f7
10 changed files with 126 additions and 127 deletions
+5 -4
View File
@@ -67,12 +67,13 @@ git tag vX.Y.Z
git push origin master --tags
```
5. Signed SQL distribution, attached to the Gitea release (Drone does this on the
tag when the repository is activated there):
5. Signed SQL distribution, attached to the GitHub release. The `release`
workflow does this on the tag, signing with the `PGMORBAC_RELEASE_KEY`
repository secret. By hand:
```bash
PGMORBAC_RELEASE_KEY=<path to the Ed25519 key> GITEA_URL=https://git.villains.fr \
GITEA_REPO=crudy/pgmorbac GITEA_TOKEN=<token> npm run release
PGMORBAC_RELEASE_KEY=<path to the Ed25519 key> GITHUB_REPOSITORY=crudylabs/pgmorbac \
GITHUB_TOKEN=<token> npm run release
```
6. The npm package `@crudy/pgmorbac` is released from the `pgmorbac-node`