fix(ci): use nonreserved github packages token#13
Conversation
Greptile SummaryThis PR fixes the CI publish workflow by renaming the secret passed to the reusable Confidence Score: 5/5Safe to merge — one-line config fix with no logic or security concerns. The change is minimal: a SHA bump to a pinned reusable workflow and a single secret mapping rename. The rename directly addresses a well-known GitHub Actions constraint on reserved secret-name prefixes, and no functionality is removed or altered. No files require special attention. Important Files Changed
Sequence DiagramsequenceDiagram
participant GH as GitHub Actions
participant PW as publish.yml
participant CT as ci-templates/js-bazel-package.yml@82308d0
participant GHCR as GitHub Packages (GHCR)
participant NPM as npm Registry
GH->>PW: Trigger (release published / workflow_dispatch)
PW->>CT: Call reusable workflow<br/>secrets: NPM_TOKEN, TINYLAND_GITHUB_PACKAGES_TOKEN
CT->>CT: Build & test (pnpm build, typecheck, unit tests)
CT->>GHCR: Publish @tinyland-inc/tinyland-auth-pg<br/>(auth via TINYLAND_GITHUB_PACKAGES_TOKEN)
CT->>NPM: Publish package<br/>(auth via NPM_TOKEN)
CT-->>PW: Job result
Reviews (1): Last reviewed commit: "fix(ci): use nonreserved github packages..." | Re-trigger Greptile |
Pins the package Publish workflow to the non-reserved token contract from ci-templates#24 and passes
TINYLAND_GITHUB_PACKAGES_TOKENwhere the workflow uses explicit secret mapping.GitHub rejects custom Actions secret names beginning with
GITHUB_, so the previousGITHUB_PACKAGES_TOKENwiring could never be installed as an org secret.Tracking: TIN-713