fix(ci): use nonreserved github packages token#6
Conversation
Greptile SummaryRenames the secret mapping from Confidence Score: 5/5Safe to merge — minimal, targeted change that unblocks org-secret installation with no logic risk. Both changes (secret rename and SHA bump) are straightforward and correctly aligned: the new secret name avoids the reserved GITHUB_ prefix, and the workflow SHA is pinned to the upstream commit that introduced the matching contract. No logic, security, or correctness issues found. 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 GPR as GitHub Packages Registry
GH->>PW: trigger (release published / workflow_dispatch)
PW->>CT: uses reusable workflow (SHA-pinned)
Note over PW,CT: secrets: NPM_TOKEN, TINYLAND_GITHUB_PACKAGES_TOKEN
CT->>GPR: publish package (authenticated via TINYLAND_GITHUB_PACKAGES_TOKEN)
GPR-->>CT: publish result
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