Use a non-reserved Cargo secret name for Gitea publishing
CI / check (push) Successful in 2m22s
Publish crates / build (push) Successful in 3m24s
Publish crates / publish-crates-io (push) Successful in 21s
Publish crates / publish-gitea (push) Successful in 28s

This commit is contained in:
Aleksandr Bogomiakov committed 2026-11-20 14:03:02 +00:00
1 parent 8af4d2cbbc
commit e47348b21d
3 files changed
+6 -6

No files matched your search

+4 -4
View File
@@ -62,11 +62,11 @@ jobs:
toolchain: "1.97"
- name: Publish mirror to Gitea without rebuilding
env:
GITEA_PACKAGES_TOKEN: ${{ secrets.GITEA_PACKAGES_TOKEN }}
CARGO_REGISTRIES_GITEA_TOKEN: ${{ secrets.CARGO_REGISTRIES_GITEA_TOKEN }}
run: |
if [ -z "$GITEA_PACKAGES_TOKEN" ]; then
echo "::error::Add the GITEA_PACKAGES_TOKEN repository Actions secret, then rerun this workflow."
if [ -z "$CARGO_REGISTRIES_GITEA_TOKEN" ]; then
echo "::error::Add the CARGO_REGISTRIES_GITEA_TOKEN repository Actions secret, then rerun this workflow."
exit 1
fi
export CARGO_REGISTRIES_GITEA_TOKEN="Bearer $GITEA_PACKAGES_TOKEN"
export CARGO_REGISTRIES_GITEA_TOKEN="Bearer $CARGO_REGISTRIES_GITEA_TOKEN"
python3 scripts/publish_crates.py --registry gitea --no-verify
+1 -1
View File
@@ -8,7 +8,7 @@ Releases `music-dht 0.6.0` and `furumi-library 0.3.0`.
- Tag-driven CI verifies release packages once, then publishes to crates.io
and the Furumi Gitea Cargo mirror in parallel jobs without recompiling.
Already published versions are skipped independently in each registry.
Authentication uses `CARGO_REGISTRY_TOKEN` and `GITEA_PACKAGES_TOKEN`.
Authentication uses `CARGO_REGISTRY_TOKEN` and `CARGO_REGISTRIES_GITEA_TOKEN`.
### Podcast discovery (`podcast_dht`)
+1 -1
View File
@@ -86,7 +86,7 @@ Add these repository Actions secrets:
- `CARGO_REGISTRY_TOKEN`: a crates.io API token with publish access to
`federation-net`, `music-dht` and `furumi-library`.
- `GITEA_PACKAGES_TOKEN`: a raw Gitea personal access token with
- `CARGO_REGISTRIES_GITEA_TOKEN`: a raw Gitea personal access token with
`write:package` and permission to publish under the `Furumi` organization.
Create it under user Settings → Applications. The workflow adds the
required `Bearer` prefix itself; no username secret is needed.