publish: repository AUDIENCE variable missing for the OIDC registry token #4

Closed
opened 2026-11-11 22:16:18 +00:00 by dsh · 1 comment
Owner

What happened

v0.1.0 is tagged (5236f85), the Forgejo release page exists, and the npmjs job skipped cleanly (no NPMJS_TOKEN). The Forgejo registry publish failed in run #775 / job #1152:

::error::Set the repository variable AUDIENCE to the authorized integration audience (u:<id>:<uuid>).

publish.yml prefers the authorized-integration OIDC token (enable-openid-connect: true + ${{ vars.AUDIENCE }}) and only falls back to NPM_TOKEN. A new repository does not inherit either from dsh-plugins/dsh-colab, so the tag cannot publish yet. The workflow itself is correct and the tests passed (61/61 in that run).

Operator action

Pick one, same as the working dsh-colab setup:

  1. OIDC (preferred): set the repository variable AUDIENCE (Settings → Actions → Variables) to the authorized-integration audience u:<id>:<uuid> used by the org, and ensure the integration has package write scope. Then re-run the failed publish workflow for v0.1.0.
  2. Token fallback: add a repository secret NPM_TOKEN with Forgejo write:package, then re-run publish.

Verification after the fix

  • pnpm view dsh-kaggle@0.1.0 version --registry https://git.pvlb.dev/api/packages/dsh-plugins/npm/ returns 0.1.0.
  • dsh plugin --profile web add --registry ... dsh-kaggle@0.1.0 installs from the registry (the linked checkout already works).
  • No retag or version bump is needed; the workflow skips an already-published version and the release page stays untouched.

Do not force-push or move v0.1.0.

## What happened `v0.1.0` is tagged (`5236f85`), the Forgejo **release page exists**, and the npmjs job skipped cleanly (no `NPMJS_TOKEN`). The Forgejo registry publish failed in run #775 / job #1152: ``` ::error::Set the repository variable AUDIENCE to the authorized integration audience (u:<id>:<uuid>). ``` `publish.yml` prefers the authorized-integration OIDC token (`enable-openid-connect: true` + `${{ vars.AUDIENCE }}`) and only falls back to `NPM_TOKEN`. A new repository does not inherit either from `dsh-plugins/dsh-colab`, so the tag cannot publish yet. The workflow itself is correct and the tests passed (61/61 in that run). ## Operator action Pick one, same as the working `dsh-colab` setup: 1. **OIDC (preferred):** set the repository variable `AUDIENCE` (Settings → Actions → Variables) to the authorized-integration audience `u:<id>:<uuid>` used by the org, and ensure the integration has package write scope. Then re-run the failed `publish` workflow for `v0.1.0`. 2. **Token fallback:** add a repository secret `NPM_TOKEN` with Forgejo `write:package`, then re-run `publish`. ## Verification after the fix - `pnpm view dsh-kaggle@0.1.0 version --registry https://git.pvlb.dev/api/packages/dsh-plugins/npm/` returns `0.1.0`. - `dsh plugin --profile web add --registry ... dsh-kaggle@0.1.0` installs from the registry (the linked checkout already works). - No retag or version bump is needed; the workflow skips an already-published version and the release page stays untouched. Do **not** force-push or move `v0.1.0`.
Author
Owner

Fixed by the operator: authorized integration is on and the AUDIENCE repository variable is set. Re-ran the failed publish workflow for v0.1.0 — success.

Verified:

  • Forgejo registry: dsh-kaggle@0.1.0, tarball https://git.pvlb.dev/api/packages/dsh-plugins/npm/dsh-kaggle/-/0.1.0/dsh-kaggle-0.1.0.tgz.
  • npmjs: dsh-kaggle@0.1.0 (created 2026-11-11T22:15:30Z).
  • Release page unchanged; no retag or version bump was needed.

Closing.

Fixed by the operator: authorized integration is on and the `AUDIENCE` repository variable is set. Re-ran the failed `publish` workflow for `v0.1.0` — **success**. Verified: - Forgejo registry: `dsh-kaggle@0.1.0`, tarball `https://git.pvlb.dev/api/packages/dsh-plugins/npm/dsh-kaggle/-/0.1.0/dsh-kaggle-0.1.0.tgz`. - npmjs: `dsh-kaggle@0.1.0` (created 2026-11-11T22:15:30Z). - Release page unchanged; no retag or version bump was needed. Closing.
dsh closed this issue 2026-11-11 22:23:35 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
dsh-plugins/dsh-kaggle#4
No description provided.