ci: pin idempotent package publish template#7
Conversation
Greptile SummaryThis PR updates the pinned commit SHA for the Confidence Score: 5/5Safe to merge — single-line SHA bump to a named idempotent workflow template with no logic changes. The PR makes exactly one change: updating a pinned full-commit SHA in a reusable-workflow reference. Pinning to a specific SHA is the recommended security practice, and the new SHA targets a well-described idempotent publish template backed by a proof run. No secrets, permissions, or build logic are touched. No files require special attention. Important Files Changed
Sequence DiagramsequenceDiagram
participant GH as GitHub (release / workflow_dispatch)
participant PY as publish.yml
participant CT as ci-templates js-bazel-package (f23f67b – idempotent)
participant NPM as npmjs
participant GHP as GitHub Packages
GH->>PY: trigger (release published or manual)
PY->>CT: uses reusable workflow @ f23f67b
CT->>CT: build / test / typecheck
CT->>NPM: publish (skip if version exists)
CT->>GHP: publish (skip if version exists)
Reviews (1): Last reviewed commit: "ci: pin idempotent package publish templ..." | Re-trigger Greptile |
Pins the shared js-bazel-package workflow to the TIN-713 idempotent publish template.
This keeps existing package publishes from failing when npmjs or GitHub Packages already has the same version.
Proof run: tinyland-inc/tinyland-stores/actions/runs/25092503866.