ci: pin idempotent package publish template#7
Conversation
Greptile SummaryThis PR updates the pinned commit SHA for the shared Confidence Score: 5/5Safe to merge — single-line SHA bump to a pinned reusable workflow with no other changes. The change is minimal (one SHA substitution), continues to use a fully-pinned commit reference (security best practice), and is backed by a successful proof run cited in the PR description. No logic, secrets, or permissions are modified. No files require special attention. Important Files Changed
Sequence DiagramsequenceDiagram
participant GH as GitHub (release / workflow_dispatch)
participant PW as publish.yml
participant CT as ci-templates js-bazel-package@f23f67b
participant NPM as npmjs / GitHub Packages
GH->>PW: trigger (release published or manual dry_run)
PW->>CT: call reusable workflow (pinned SHA)
CT->>CT: typecheck, test, build, package-check
CT->>NPM: publish (idempotent — skip if version already exists)
NPM-->>CT: success (or "already exists" — no failure)
CT-->>PW: workflow complete
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.