fix(ci): update publish workflow ci-templates SHA#67
Conversation
Greptile SummaryThis PR updates the Confidence Score: 5/5Safe to merge — single-line SHA bump that aligns publish.yml with the already-working ci.yml reference. The change is a one-line SHA update with a clear, documented rationale. Both workflows now reference the same ci-templates commit, restoring the publish path that was broken by the missed update in #66. No logic, configuration, or secrets handling is modified. No files require special attention. Important Files Changed
Sequence DiagramsequenceDiagram
participant GH as GitHub
participant PW as publish.yml
participant CT as ci-templates<br/>js-bazel-package.yml<br/>@f2e12c1
participant Runner as Self-hosted Runner
GH->>PW: release published / workflow_dispatch
PW->>CT: uses: reusable workflow (top-level permissions)
CT->>Runner: spawn jobs (lint, typecheck, test, build, package)
Runner-->>CT: job results
CT-->>PW: workflow conclusion
PW-->>GH: publish outcome
Reviews (1): Last reviewed commit: "fix(ci): update publish workflow ci-temp..." | Re-trigger Greptile |
Summary
publish.yml) still pinned to ci-templates@0e13cc4which has per-jobpermissionsblocks causingstartup_failure@f2e12c1(ci-templates PRs refactor!: remove middleware (belongs in acuity-middleware) #10 + feat: v0.5.0 - remove acuity-scraper, add Bazel 8 config #11)Without this fix, any tag push or release creation will fail with
startup_failurebefore jobs are created.Tracked