name: CI

# IMPORTANT — the currently inventoried server is Gitea 1.24.2, which *ignores* several keys used
# below. Per https://docs.gitea.com/1.24/usage/actions/comparison, its unsupported workflow syntax
# includes `permissions` / `jobs.<job_id>.permissions`, `concurrency`, and
# `jobs.<job_id>.timeout-minutes`. They are declared here deliberately, so the workflow is already
# correct on a supported release and on GitHub Actions, but on this server they are inert:
#
#   * `permissions:` does NOT restrict the in-job `GITEA_TOKEN`. Job-token permission controls,
#     repository/owner defaults, and server-side maximum-permission clamping arrive in the 1.26
#     feature line (https://docs.gitea.com/1.26/usage/actions/token-permissions). Until the server
#     is upgraded and configured, the token's authority is whatever the server grants — not what
#     this file requests.
#   * `concurrency:` and `timeout-minutes:` are NOT bounded-execution guarantees here. Cancellation,
#     timeout, and teardown must be enforced by the trusted runner provisioner/reaper.
#
# `persist-credentials: false` below is unaffected by any of this and is enforced by the action
# itself. See docs/development/security.md.

on:
  pull_request:
  push:
    branches:
      - main

permissions:
  contents: read

concurrency:
  group: ci-${{ github.workflow }}-${{ github.ref }}
  cancel-in-progress: true

jobs:
  verify:
    runs-on: ubuntu-latest
    timeout-minutes: 15
    steps:
      - name: Check out repository
        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
        with:
          # `actions/checkout` defaults to leaving the job token in `.git/config`, where any later
          # step — including one a pull request added to this file — could read or reuse it. Nothing
          # in this workflow pushes, so the credential is never needed after checkout.
          persist-credentials: false

      - name: Set up Node.js
        uses: actions/setup-node@48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e # v6.4.0
        with:
          node-version-file: .node-version

      - name: Activate pinned pnpm
        run: |
          corepack enable
          corepack prepare pnpm@11.12.0 --activate

      - name: Install dependencies
        run: pnpm install --frozen-lockfile

      - name: Verify repository
        run: pnpm ci:verify

  infrastructure-smoke:
    needs: verify
    runs-on: ubuntu-latest
    timeout-minutes: 10
    steps:
      - name: Check out repository
        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
        with:
          # `actions/checkout` defaults to leaving the job token in `.git/config`, where any later
          # step — including one a pull request added to this file — could read or reuse it. Nothing
          # in this workflow pushes, so the credential is never needed after checkout.
          persist-credentials: false

      - name: Exercise PostgreSQL and S3 infrastructure
        run: bash scripts/smoke-infrastructure.sh

  migration-smoke:
    needs: verify
    runs-on: ubuntu-latest
    timeout-minutes: 15
    steps:
      - name: Check out repository
        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
        with:
          # `actions/checkout` defaults to leaving the job token in `.git/config`, where any later
          # step — including one a pull request added to this file — could read or reuse it. Nothing
          # in this workflow pushes, so the credential is never needed after checkout.
          persist-credentials: false

      - name: Set up Node.js
        uses: actions/setup-node@48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e # v6.4.0
        with:
          node-version-file: .node-version

      - name: Activate pinned pnpm
        run: |
          corepack enable
          corepack prepare pnpm@11.12.0 --activate

      - name: Install dependencies
        run: pnpm install --frozen-lockfile

      - name: Exercise transactional migrations against PostgreSQL
        run: pnpm test:migrations:integration