Deployment

Crons deploy from the node-backend monorepo (crons/ directory). CI and manual deploys always run the API stack first, then this stack.

Automatic deploys

Same GitHub Actions workflows as the API (deploy-dev.js.yml, deploy-prod.js.yml):

Gameslib (and similar) should dispatch dep_update_* only to node-backend — both stacks redeploy from one workflow.

PR CI: .github/workflows/test.yml job test-crons runs lint:crons, test:crons, and test:crons:layers.

AP dependency pins

AP pins live in the repo-root ci-deps.dev.json and ci-deps.prod.json (gameslib, renderer, recranks). Root npm run sync-deps runs ap-install-deps, scripts/sync-crons-ap-deps.mjs (copies root AP pins into crons/package.json), then scripts/prune-crons-nested-ap-deps.mjs (drops stale crons/node_modules/@abstractplay and reconciles the lockfile). CI runs sync-crons-ap-deps before npm ci so you do not need to hand-edit crons/package.json after dep bumps or merges.

Do not run ap-install-deps or npm install for AP packages from crons/ alone — use root npm run sync-deps.

Manual deploy

From repo root (after API deploy):

npm run build -w abstractplay-backend-crons   # eslint in crons/
npm run test:crons:layers                     # optional but recommended
bash crons/scripts/serverless-deploy.sh dev   # or prod

Or from crons/:

cd crons
npm run build
npm run test:layers
npx serverless deploy --stage dev

AWS profile comes from params in serverless.yml (AbstractPlayDev / AbstractPlayProd).

Schedules

EventBridge cron rules are enabled only on prod (custom.scheduleEnabled.prod: true). Dev stacks contain the Lambdas but scheduled invocations are off.

Ops alerts (email)

On prod, CloudWatch alarms in this stack publish to the SNS topic exported by the API stack (abstract-play-prod-OpsAlertsTopicArn). Confirm the ops-alerts email subscription via node-backend deployment.

Crons alarms include records, summarize, thumbnails, thumbnails-verify, thumbnail render (sqs-to-render, custom RenderFailure, render DLQ).

Documentation site

Cron docs live in crons/docs/ and publish under /crons/ on the docs site. The AbstractPlay/docs prebuild syncs vendor/node-backend/crons/docs (no separate backend-crons submodule). Maintainer checklist: _docs-repo-integration.md.

Related

• Pipeline
• Backend deployment