Release events@2.4.0, accounts@1.0.0, contracts@1.5.0 and agent@1.1.0
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -1,10 +1,9 @@
|
||||
# Accounts 1.0.0 — one sign-in for every product of a church
|
||||
|
||||
Phase **3** of [ROADMAP-v3.md](./ROADMAP-v3.md) (§3, §8, §9; decisions 2, 14, 15, 17). Written
|
||||
2026-11-18. **Decisions confirmed 2026-11-18** (all as proposed). **Built 2026-11-18** on branches (not
|
||||
merged): `feat/accounts-1.0` here (the app, contracts 1.5.0, `packages/auth-client`, `packages/ui`,
|
||||
`crosscode install`/`add`, agent 1.1.0), `feat/accounts-install` in events-hub (Hub 2.3.0),
|
||||
`feat/one-sign-in` in crosscode-site. Not yet: the VM test and a real Postgres (on another device). See [Changes while building](#changes-while-building).
|
||||
2026-11-18. **Decisions confirmed 2026-11-18** (all as proposed). **Released 2026-11-18** (`accounts@1.0.0`,
|
||||
`contracts@1.5.0`, `agent@1.1.0`, Hub `v2.3.0`, crosscode-site `v1.5.0`). Not yet: the VM test and a run
|
||||
on real Postgres (on another device), before it's installed for a church.
|
||||
|
||||
**What Accounts is:** a small OpenID Connect provider per church, at `accounts.<church's address>`.
|
||||
People sign in there once and are signed in to all of the church's products. Members never see it
|
||||
|
||||
@@ -1,10 +1,10 @@
|
||||
# Cross Events 2.4.0 — protocol v2, Linked products, the event feed and `packages/seo`
|
||||
|
||||
Phase **2** of [ROADMAP-v3.md](./ROADMAP-v3.md) (§4, §5 "Sibling discovery", §9, §11; decisions
|
||||
5, 20). Written 2026-11-18. **Built 2026-11-18** on branches (contracts 1.4.0 and Events 2.4.0 on
|
||||
`feat/events-2.4` here, Hub 2.2.0 on `feat/link-public-key`, crosscode-site on
|
||||
`feat/linked-products`); not tagged yet. The decisions below were taken as proposed. Where the
|
||||
build differs from this plan, see [Changes while building](#changes-while-building).
|
||||
5, 20). Written 2026-11-18. **Released 2026-11-18** (`events@2.4.0`, `contracts@1.4.0`, Hub `v2.2.0`, crosscode-site `v1.4.0`),
|
||||
before the e2e run on Postgres and the VM test, which come before any church gets it. The
|
||||
decisions below were taken as proposed. Where the build differs from this plan, see
|
||||
[Changes while building](#changes-while-building).
|
||||
|
||||
**What 2.4.0 is:** Cross Events becomes a full member of a church stack. It reports to the Hub as
|
||||
`product: "events"` (protocol v2), shows the church's other products under **Settings → Linked
|
||||
|
||||
+2
-2
@@ -28,8 +28,8 @@ for each phase and the rollout checklist ([ROLLOUT-1.0.md](./ROLLOUT-1.0.md)).
|
||||
| 1b | Cross Events 2.2.0: moved here as `apps/events`, the `crosscode` script | **Released** 2026-11-17 (`events@2.2.0`, with AI use in tokens and the backend under `/api`). **VM tested 2026-11-17** (EVENTS-2.2-PLAN §6, all passing after fixes). **Not rolled out:** servers still run `hope-events` `v2.1.1` until each install is adopted |
|
||||
| 1c | Cross Events 2.3.x: authenticator app 2FA (TOTP + recovery codes) | **Released** 2026-11-17 (`events@2.3.0`). **`events@2.3.1`** 2026-11-18: Next.js 16.4.6 (security advisories for 16.2.0–16.4.4), so roll out 2.3.1, not 2.3.0. crosscode-site `v1.3.0` lists it (merged and tagged, **not deployed**) |
|
||||
| 1d | Agent 1.0.x + Hub 2.1.x (+ contracts 1.3.0) | **Released** 2026-11-17 (`agent@1.0.0`, `contracts@1.3.0`, Hub `v2.1.0`). **VM tested** end to end (AGENT-1.0-PLAN §13: joins, installs behind frp, scheduled / batch / missed updates, uninstall with export and purge, forged and replayed jobs). 2026-11-18: **`agent@1.0.1`** (the agent answers status on the central server itself) and Hub **`v2.1.1`** (adopt passes the church's address; Link takes the short name as a name). **Not rolled out**: use agent 1.0.1 and Hub 2.1.1 |
|
||||
| 2 | Cross Events 2.4.0: protocol v2, Linked products, event feed, `packages/seo` (+ contracts 1.4.0, Hub 2.2.0) | **Built** 2026-11-18 ([EVENTS-2.4-PLAN.md](./EVENTS-2.4-PLAN.md), decisions taken as proposed, "Changes while building" there): `feat/events-2.4` here, `feat/link-public-key` in events-hub, `feat/linked-products` in crosscode-site. Unit tests pass. **Not tagged:** the e2e spec and the VM test haven't run (no Postgres on the dev machine) |
|
||||
| 3 | Accounts 1.0.0 (+ contracts 1.5.0, agent 1.1.0, Hub 2.3.0) | **Built** 2026-11-18 ([ACCOUNTS-1.0-PLAN.md](./ACCOUNTS-1.0-PLAN.md), decisions confirmed) on `feat/accounts-1.0` here, `feat/accounts-install` in events-hub, `feat/one-sign-in` in crosscode-site; not merged. 37 backend tests and 8 Playwright tests pass (no Postgres needed). **Still to do:** the VM test and a run on real Postgres (another device), then release |
|
||||
| 2 | Cross Events 2.4.0: protocol v2, Linked products, event feed, `packages/seo` (+ contracts 1.4.0, Hub 2.2.0) | **Released** 2026-11-18 (`events@2.4.0`, `contracts@1.4.0`, Hub `v2.2.0`, crosscode-site `v1.4.0`; [EVENTS-2.4-PLAN.md](./EVENTS-2.4-PLAN.md)). **Before any church gets it:** the Events e2e run on Postgres and the VM test (EVENTS-2.4-PLAN §8) |
|
||||
| 3 | Accounts 1.0.0 (+ contracts 1.5.0, agent 1.1.0, Hub 2.3.0) | **Released** 2026-11-18 (`accounts@1.0.0`, `contracts@1.5.0`, `agent@1.1.0`, Hub `v2.3.0`, crosscode-site `v1.5.0`; [ACCOUNTS-1.0-PLAN.md](./ACCOUNTS-1.0-PLAN.md)). 37 backend and 8 Playwright tests pass without Postgres. **Before installing it for a church:** the VM test and a run on real Postgres; a Hub release source for `accounts@` tags |
|
||||
| 4–7 | Website 1.0.0 → Events 3.0.0 → App 1.0.0 → App 1.x | Not started |
|
||||
|
||||
## Next up
|
||||
|
||||
Reference in New Issue
Block a user