fix(ci): use nonreserved github packages token#6
Conversation
Greptile SummaryRenames the secret passed to the reusable publish workflow from Confidence Score: 5/5Safe to merge — minimal, targeted CI fix with no logic changes. Both changes are mechanical and correct: the secret rename unblocks org-level provisioning (GitHub's reserved-prefix constraint), and the SHA bump pins to the corresponding ci-templates release. No logic, no new dependencies, and no security concerns introduced. No files require special attention. Important Files Changed
Sequence DiagramsequenceDiagram
participant GH as GitHub Actions
participant PW as publish.yml
participant RW as ci-templates/js-bazel-package.yml@82308d06
GH->>PW: trigger (release / workflow_dispatch)
PW->>RW: call reusable workflow
note over PW,RW: secrets: NPM_TOKEN, TINYLAND_GITHUB_PACKAGES_TOKEN
RW->>GH: publish to npm + GitHub Packages
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