diff --git a/.github/workflows/publish.yml b/.github/workflows/publish.yml index 9fd89d5..53fd3bf 100644 --- a/.github/workflows/publish.yml +++ b/.github/workflows/publish.yml @@ -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 diff --git a/CHANGELOG.md b/CHANGELOG.md index 849437b..580c308 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -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`) diff --git a/README.md b/README.md index 5e20f16..a6b650d 100644 --- a/README.md +++ b/README.md @@ -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.