Files
crosscode-platform/CHANGELOG.md
T
2026-11-17 22:23:11 +02:00

5.4 KiB

Changelog

Each package and app has its own section and its own tags (contracts@1.0.0, accounts@1.0.0, …).

events@2.3.0, contracts@1.3.0, agent@1.0.0 - 2026-11-17

Phase 1c (authenticator-app sign-in) and phase 1d (docs/AGENT-1.0-PLAN.md): installs, updates and uninstalls from the Hub (Hub 2.1.0) through the agent. Tested end to end on a VM (church server + central server + Hub, AGENT-1.0-PLAN §13 and EVENTS-2.2-PLAN §6).

Events (2.3.0)

  • Two-factor with an authenticator app, and recovery codes. The env template, the church export and registering by itself from HUB_LICENCE_KEY for installs from the Hub. Details in apps/events/CHANGELOG.md.

Contracts (1.3.0)

  • crosscode.agent-job/1 (fixed job types, strict arguments), crosscode.agent-report/1, crosscode.script-report/1, crosscode.agent-stats/1, the agent join / poll requests, crosscode.env-template/1 and crosscode.church-export/1.
  • @crosscode/contracts/signing: Ed25519 jobs (over canonical JSON) and agent requests, config sealed to a server (X25519 + HKDF + AES-256-GCM), export encryption.

Agent (1.0.0)

  • apps/agent: polls the Hub, checks every job (pinned key, server, time window, replays, type, arguments) and runs the crosscode script for it; stats every minute; listens on nothing. Install script, systemd unit, self-update with automatic revert.

crosscode script

  • --json reports and --config on every command; .env files from each release's env template (appended to, never rewritten, on deploy); install --frp with Hub-given ports, a database on another server, and clean-up on failure; frpc.ini blocks; restart, export, uninstall, purge.
  • Fixed in the VM test: adopt applies a release's new migrations in the switch-over; a failed migration is marked rolled back so later deploys aren't blocked; frpc is restarted once when its admin lines are first added; a site's PM2 always runs under its own systemd unit (pm2-<user>), so restarting or updating the agent never stops a site; tags are fetched with --force.

events@2.2.0, contracts@1.2.0 - 2026-11-17

Events

  • Cross Events 2.2.0, the first release from this repo (apps/events, ROADMAP-v3 phase 1b): moved in with its history, npm workspaces with one root lockfile, and the crosscode script (deploy, status, install, adopt) in scripts/. Also AI use shown in tokens instead of rand, and everything the backend serves under /api. Details in apps/events/CHANGELOG.md.

Contracts

  • AI status (Hub protocol §3b): optional usedInputTokens, usedOutputTokens, capInputTokens, capOutputTokens (Hub 2.0.1). Churches see tokens; the cents stay for the Hub and older installs.

Docs

  • The roadmap (docs/ROADMAP-v3.md) and the Hub protocol (docs/hub-protocol.md) move here from hope-events/docs/, since they cover every product. New: docs/HANDOVER.md (where each phase stands) and docs/EVENTS-2.2-PLAN.md (phase 1b, Cross Events into the monorepo).

contracts@1.1.0 - 2026-11-04

Contracts

  • Hub protocol v2: optional requires on a release ([{ product, version }]), the sibling versions it needs. The Hub refuses an update request with 409 REQUIREMENT_NOT_MET until they're met (Hub 2.0, ROADMAP-v3 §5). Optional, so the schema stays /1-compatible.

contracts@1.0.0 - 2026-11-04

Monorepo

  • Set up: npm workspaces (packages/*, apps/*), shared TypeScript, ESLint and Jest setup, and npm run check (lint, typecheck, tests and build).
  • packages/contracts: package set up with a dual CommonJS / ESM build (tsup) and the schema-name helpers every contract uses (crosscode.<name>/<major>).
  • packages/ui, apps/accounts, apps/website, apps/app: placeholders.

Contracts

  • crosscode.event/1 and crosscode.event-feed/1: the event, the feed response and the event.changed webhook. Checks that startsAt / endsAt match the sessions and that only Cross Events takes registrations. parseEventFeed skips and reports a bad event instead of failing the whole feed; eventKey is the cross-product id.
  • crosscode.church/1: the church profile (branding, campuses, service times, contact, links).
  • crosscode.identity/1: sign-in claims (no roles; 2FA method including the authenticator app, news consent, privacy notice version) and the user.updated, user.deleted (with a "deferred" reply) and user.export back-channel calls.
  • Sign-in return: isSafeReturnPath, safeReturnPath, encodeState / decodeState and isRegisteredRedirectUri, so every product sends people back to the page they came from in the same safe way.
  • Hub protocol v2: product on register and heartbeat, stats per product (Events as in v1; Website storage and App active-member bands for billing), the install's public key, linked products in the replies, customerId / product in the licence token.
  • @crosscode/contracts/signing (Node only): the Hub's HMAC scheme for the Hub and product links.
  • Sample payloads for every contract in samples/, checked by the tests.
  • JSON Schema (draft 2020-12) for every contract in schemas/, generated from the zod schemas by npm run build (scripts/json-schemas.cjs), for consumers that don't use TypeScript or zod. A test checks the files match the zod schemas and that every sample passes them (Ajv). Checks JSON Schema can't express (e.g. startsAt matching the sessions) only run in zod.