Skip to content

Install the shared CAIL packages from public npm - #17

Merged
szweibel merged 1 commit into
mainfrom
agent/cail-packages-from-npm
Sep 28, 2026
Merged

szweibel merged 1 commit into
mainfrom
agent/cail-packages-from-npm

Conversation

@szweibel

Copy link
Copy Markdown
Contributor

The shared @cuny-ai-lab packages (cail-log 0.6.4, cail-identity 5.2.6, cail-client 6.2.2) are now on public npm. Slide Maker already pinned those versions; this moves CI and the release host off GitHub Packages so installs need no token.

Changes

  • .npmrc: scope mapped to https://registry.npmjs.org.
  • pnpm-lock.yaml: the three packages resolve from npm (0 npm.pkg.github.com URLs; only their integrity lines changed).
  • ci.yml: removed packages: read, registry-url/scope, and NODE_AUTH_TOKEN.
  • deploy.yml: removed packages: read.
  • scripts/release/host.mjs: dropped the temporary .release-npmrc that passed the SSH-supplied token to pnpm install; asserts the tracked .npmrc now points at npm. The token is still used to verify the release source through the GitHub API.
  • scripts/release/contract.mjs + test: NODE_AUTH_TOKEN is no longer a deployment credential, so it is no longer in the rejected application-environment keys (GITHUB_TOKEN rejection and its test remain).
  • README: packages install from public npm with no token.

Verified (clean HOME, empty NODE_AUTH_TOKEN, pnpm 9.15.0)

  • pnpm install --frozen-lockfile, pnpm --filter @slide-maker/web check, pnpm build, pnpm test (724 passed, 8 skipped), node --test scripts/release/*.test.mjs (14 passed), playwright test --config e2e/fleet.config.ts (1 passed): all exit 0.
  • actionlint clean on both workflows.
  • Not exercised: the production release path on the host (no deploy run).

🤖 Generated with Claude Code

cail-log 0.6.4, cail-identity 5.2.6 and cail-client 6.2.2 are now on the
public npm registry, so neither CI nor the release host needs a GitHub
Packages credential to install them. Map the @CUNY-AI-Lab scope to
registry.npmjs.org in .npmrc, regenerate pnpm-lock.yaml against npm, and
remove the token plumbing: the CI registry setup and NODE_AUTH_TOKEN, the
packages: read permissions, and the release host's temporary .npmrc that
fed the SSH-supplied token to pnpm. The host still uses that token to
verify the release source, and now asserts the tracked .npmrc points at
npm. NODE_AUTH_TOKEN is no longer a deployment credential, so the
production-environment contract stops listing it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@szweibel
szweibel merged commit 282d718 into main Sep 28, 2026
2 checks passed
@szweibel
szweibel deleted the agent/cail-packages-from-npm branch September 28, 2026 17:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant