ci: pin idempotent package publish template#11
Conversation
Greptile SummaryThis PR updates the pinned SHA reference for the shared Confidence Score: 5/5Safe to merge — single SHA bump on a pinned reusable workflow with no logic changes. The change is a one-line SHA update that keeps the workflow pinned to an immutable commit, following GitHub Actions security best practices. No permissions, secrets handling, logic, or other configuration is modified. The proof run cited in the PR description confirms the new SHA behaves as intended. No files require special attention. Important Files Changed
Sequence DiagramsequenceDiagram
participant GH as GitHub Actions
participant PY as publish.yml
participant CT as ci-templates<br/>(js-bazel-package.yml<br/>@ f23f67b)
participant NPM as npmjs / GitHub Packages
GH->>PY: release published / workflow_dispatch
PY->>CT: call reusable workflow (pinned SHA)
CT->>CT: build, typecheck, test
CT->>NPM: publish (idempotent – skip if version exists)
NPM-->>CT: 200 OK or "already exists" (no error)
CT-->>PY: success
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.