ci: pin idempotent package publish template#7
Conversation
Greptile SummaryThis PR updates the pinned SHA of the shared Confidence Score: 5/5Safe to merge — single-line SHA bump to a SHA-pinned reusable workflow with no other changes. The change is limited to updating a pinned SHA reference in a reusable workflow call. SHA-pinning is the correct security practice for third-party or shared Actions, and the PR description links a successful proof run validating the new template behavior. No files require special attention. Important Files Changed
Sequence DiagramsequenceDiagram
participant GH as GitHub Release / workflow_dispatch
participant PW as publish.yml (this repo)
participant CT as ci-templates js-bazel-package.yml@f23f67b
participant NPM as npmjs
participant GHP as GitHub Packages
GH->>PW: trigger (release published or manual)
PW->>CT: uses reusable workflow (pinned SHA)
CT->>CT: build, typecheck, test, package check
CT->>NPM: publish (idempotent – skip if version exists)
CT->>GHP: publish (idempotent – 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.