Isolate npm publish from PR CI, enforce frozen lockfiles and a 24h minimumReleaseAge, and document safe pull_request_target usage so fork PRs cannot reach publish credentials. Co-authored-by: Rotimi Best <rotimi-best@users.noreply.github.com>
35 lines
888 B
YAML
35 lines
888 B
YAML
name: Publish @classroomio/mcp to NPM
|
|
|
|
# Publish-only. Never triggered by pull_request — keeps NPM_TOKEN off the PR trust boundary.
|
|
# PR/push build verification lives in mcp-package-build-check.yml.
|
|
|
|
on:
|
|
workflow_dispatch:
|
|
|
|
jobs:
|
|
publish:
|
|
runs-on: ubuntu-latest
|
|
environment: production
|
|
permissions:
|
|
contents: read
|
|
steps:
|
|
- uses: actions/checkout@v4
|
|
|
|
- uses: actions/setup-node@v4
|
|
with:
|
|
node-version: 20.19.3
|
|
registry-url: 'https://registry.npmjs.org'
|
|
|
|
- uses: pnpm/action-setup@v4
|
|
|
|
- name: Install dependencies
|
|
run: pnpm install --frozen-lockfile
|
|
|
|
- name: Build publishable MCP package
|
|
run: pnpm mcp:build
|
|
|
|
- name: Publish package
|
|
run: pnpm --filter @classroomio/mcp publish --no-git-checks --access public
|
|
env:
|
|
NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
|