fix(ci): use package-token capable publish workflow#7
Conversation
Greptile SummaryThis PR bumps the pinned SHA for the reusable Confidence Score: 5/5Safe to merge — minimal, targeted SHA pin update with no logic changes. The only change is a SHA reference bump for a trusted internal org workflow. SHA pinning is the correct security practice, No files require special attention. Important Files Changed
Sequence DiagramsequenceDiagram
participant GH as GitHub Actions
participant CI as ci.yml (tinyland-security)
participant TPL as js-bazel-package.yml@0d88ad7<br/>(ci-templates#22)
participant GPR as GitHub Packages Registry
GH->>CI: trigger (push/tag/PR/dispatch)
CI->>TPL: call reusable workflow<br/>(secrets: inherit)
TPL->>TPL: build, typecheck, test
alt publish == true OR tag push
TPL->>GPR: publish @tinyland-inc/tinyland-security<br/>using GITHUB_PACKAGES_TOKEN
else
TPL->>TPL: dry_run (no publish)
end
TPL-->>CI: workflow result
Reviews (1): Last reviewed commit: "fix(ci): use package-token capable publi..." | Re-trigger Greptile |
Summary
js-bazel-package.ymlpin to ci-templates#22GITHUB_PACKAGES_TOKENsecret to be used for GitHub Packages publicationValidation
ruby -e 'require "yaml"; YAML.load_file(".github/workflows/ci.yml")'git diff --check