Skip to content

chore(release): promote develop to main #11

chore(release): promote develop to main

chore(release): promote develop to main #11

Workflow file for this run

name: MCP Transport Parity
# Diffs the remote MCP bridge against the stdio package against one live
# AutoMem. See docs/MCP_TRANSPORT_PARITY.md for the contract.
#
# No scheduled run yet, deliberately. While the harness is intentionally red
# against the known gaps, `continue-on-error` leaves the workflow successful
# either way, so a cron job could not distinguish "same known gaps" from "a
# newly published mcp-automem added drift" — it would be an alarm that cannot
# alarm. The weekly drift check lands with the change that turns the harness
# green, where a failure is a real signal.
on:
pull_request:
paths:
- 'mcp-sse-server/**'
- 'automem/api/**'
- 'app.py'
workflow_dispatch:
jobs:
parity:
runs-on: ubuntu-latest
# Phase 1 only. The harness is legitimately red until the bridge is moved
# onto the shared MCP surface; this is removed in the same change.
continue-on-error: true
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: '20'
cache: npm
cache-dependency-path: mcp-sse-server/package-lock.json
- name: Start AutoMem stack
env:
AUTOMEM_API_HOST_PORT: '8011'
AUTOMEM_API_TOKEN: test-token
ADMIN_API_TOKEN: test-admin-token
run: docker compose up -d
- name: Wait for /health
run: |
for i in $(seq 1 60); do
if curl -fsS http://localhost:8011/health > /dev/null; then
echo "AutoMem is up after ${i}s"
exit 0
fi
sleep 1
done
echo "AutoMem did not become healthy within 60s"
docker compose logs flask-api
exit 1
- name: Run parity harness
working-directory: mcp-sse-server
env:
AUTOMEM_RUN_PARITY_TESTS: '1'
AUTOMEM_PARITY_API_URL: http://localhost:8011
AUTOMEM_PARITY_API_TOKEN: test-token
run: |
npm ci
node -p "'stdio package under test: ' + require('@verygoodplugins/mcp-automem/package.json').version"
npm test
- name: Dump service logs on failure
if: failure()
run: docker compose logs --tail=200