Make requirements WHAT-focused: drop implementation details #47

	name: CI

	on:
	push:
	branches: [master, v2-poc-requirements]
	pull_request:

	jobs:
	checks:
	name: Build, lint, unit + integration tests
	runs-on: ubuntu-latest
	timeout-minutes: 15
	steps:
	- uses: actions/checkout@v4
	# Installs the pnpm version pinned by package.json's `packageManager` field; must run
	# before setup-node so its `cache: pnpm` can find the pnpm store.
	- uses: pnpm/action-setup@v4
	- uses: actions/setup-node@v4
	with:
	node-version: 24
	cache: pnpm
	- run: pnpm install --frozen-lockfile
	- run: pnpm run build
	- run: pnpm run lint
	- run: pnpm run format:check
	- run: pnpm test

	e2e:
	name: Actor dev-loop e2e (apify-cli + Docker)
	runs-on: ubuntu-latest
	timeout-minutes: 30
	steps:
	- uses: actions/checkout@v4
	- uses: pnpm/action-setup@v4
	- uses: actions/setup-node@v4
	with:
	node-version: 24
	cache: pnpm
	- run: pnpm install --frozen-lockfile
	# The suite manages Docker itself against the runner's daemon: it pre-pulls the
	# Actor base images, builds the runtime image, starts the runtime container with
	# the host Docker socket, and drives it with stock apify-cli via npx.
	- run: pnpm run test:e2e
	# The e2e's runtime container is normally removed by the suite's afterAll; on
	# failure it is left running, so its server-side view of any failed request
	# (log-stream lifecycle included) is captured here for diagnosis.
	- name: Dump runtime container logs on failure
	if: failure()
	run: docker logs actor-runtime-e2e --tail 300 \|\| true

Navigation Menu