db-migrations: use pg for new migrations #366

	name: Standard E2E Tests

	on:
	push:
	pull_request:

	env:
	LOG_LEVEL: DEBUG

	jobs:
	standard-e2e:
	timeout-minutes: 15
	# TODO should we use the same container as circle & central?
	runs-on: ubuntu-latest
	services:
	# see: https://docs.github.com/en/[email protected]/actions/using-containerized-services/creating-postgresql-service-containers
	postgres:
	image: postgres:14.10
	env:
	POSTGRES_PASSWORD: odktest
	ports:
	- 5432:5432
	# Set health checks to wait until postgres has started
	options: >-
	--health-cmd pg_isready
	--health-interval 10s
	--health-timeout 5s
	--health-retries 5
	steps:
	- uses: actions/checkout@v4
	- name: Set node version
	uses: actions/setup-node@v4
	with:
	node-version: 22.12.0
	cache: 'npm'
	- run: npm ci
	- run: node lib/bin/create-docker-databases.js

	- name: E2E Test
	timeout-minutes: 10
	run: ./test/e2e/standard/run-tests.sh

	- uses: ./.github/actions/install-postgres-client
	with:
	postgres-version: 14
	- name: Grant postgres superuser role
	# As per #1368, this role is required to create the pgrowlocks extension
	run: psql -c 'ALTER ROLE jubilant SUPERUSER' postgresql://postgres:odktest@localhost/postgres
	- name: Backup/restore tests
	timeout-minutes: 10
	run: ./test/e2e/standard/backup-restore.sh

	- name: Backend Logs
	if: always()
	run: "! [[ -f ./server.log ]] \|\| cat ./server.log"

Provide feedback