Skip to content

The cross-harness, self-improving memory layer for AI agents. Join our community: https://discord.com/invite/zdNChS2fBu

ci(npm-publish-sdk): pin actions by SHA, like the release workflows (#1167)

kyle-elliott-asymptote0f9a6256ccf5
diff --git a/.github/workflows/npm-publish-sdk.yml b/.github/workflows/npm-publish-sdk.yml
index f98e50b2..1cbfa2db 100644
--- a/.github/workflows/npm-publish-sdk.yml
+++ b/.github/workflows/npm-publish-sdk.yml
@@ -31,8 +31,8 @@ jobs:
run: |
echo "npm publish runs only from an sdk-js-v* tag (got ${GITHUB_REF})" >&2
exit 1
- - uses: actions/checkout@v7
- - uses: actions/setup-node@v7
+ - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
+ - uses: actions/setup-node@949feb2413d6458794dcd2491c4babbbce0c15c1 # v7.1.0
with:
node-version: 24
registry-url: https://registry.npmjs.org
diff --git a/CLAUDE.md b/CLAUDE.md
index 7476b819..0c4844ce 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -292,9 +292,11 @@ A pushed `v*` tag runs the full release end-to-end via
workflow's OIDC token) for every file `checksums.txt` lists. It needs
`id-token: write` and `attestations: write` and no `release`-environment secrets.
-Every third-party action in `release.yml` and `release-extension.yml` is pinned to
-a full commit SHA with the version in a trailing comment, because these jobs hold
-the signing secrets. Bump them by SHA, never back to a tag.
+Every third-party action in `release.yml`, `release-extension.yml` and
+`npm-publish-sdk.yml` is pinned to a full commit SHA with the version in a
+trailing comment, because these jobs hold the signing secrets or, for the SDK,
+the `id-token` npm's trusted publisher accepts. Bump them by SHA, never back to
+a tag.
Required `release`-environment secrets: `HOMEBREW_TAP_TOKEN`,
`DEVELOPER_ID_APP_CERT_P12`, `DEVELOPER_ID_APP_CERT_PASSWORD`,