Migrate lunacycle to celilo_contract 2.0 #74
No reviewers
Labels
No labels
area/auth
area/backend
area/ci
area/deploy
area/e2e
area/frontend
area/shared
blocked
good-first-issue
needs-info
priority/high
priority/low
priority/medium
type/bug
type/chore
type/docs
type/feature
type/tech-debt
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
celilo/lunacycle!74
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/contract-2"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Three files, branched from current
main. This is the mergeable one — see the note about #73 at the bottom.celilo-mgr runs CLI 5.1.0, which retired
celilo_contract1.0, so this module is currently undeployable: any deploy fails aton_installwithThe bump was not safe on its own
on_installminted an authentik API token and returned it as a hook output, relying on celilo to persist it as the module secretsmoketest_bot_token. Contract 2.0 retires exactly that channel: the value is persisted nowhere and the deploy still reports success. Bumping the line alone would have shipped precisely the silent loss the retirement exists to surface.The correct port is deletion, not
secrets.set:health-check.ts,smoke-handler.tsandscripts/smoke/authentik-token.tseach document why an authentik API token cannot drive the smoke path, which authenticates by OIDC login insteadThe mint and its log line are kept; removing those is a behavioural change beyond this migration.
version: 1.6.0 → 1.6.1,celilo_contract: "1.0" → "2.0".Gates:
typecheck:hooks0,test:hooks67 pass / 0 fail. The test now asserts the hook returns{}— on the parallel branch this same assertion was verified to fail when the write is re-introduced (11 pass → 10 pass / 1 fail).About #73
I opened #73 first from
fix-e2e-seed-unique(the WIP branch). It cannot merge: that branch andmainhave unrelated histories —git mergerefuses outright — and its manifest reads 1.4.3 against main's 1.6.0, so merging it would also be a version downgrade. Treat #73 as a review vehicle for the feature work, not a merge candidate, and take the contract migration from here instead.After merge
Publishing needs a site build:
site/distis gitignored and the module ships its built site, which is also why lunacycle currently reads ERROR on the fleet (no built site at /var/celilo/modules/lunacycle/site/dist).Part of the fleet-wide migration: celilo#1419, bead
ce-h2w0,lu-ku2.