celilo/homepage
2
0
Fork 0
Code Issues 1 Pull requests Projects Releases Packages Wiki Activity Actions

Migrate peterbanka-org to celilo_contract 2.0 #6

Merged
forgejo-admin merged 1 commit from fix/contract-2 into main 2026-09-27 01:03:12 +00:00
Conversation 0 Commits 1 Files changed 1 +2 -2
forgejo-admin commented 2026-09-26 20:54:12 +00:00
Owner
Copy link

celilo-mgr runs CLI 5.1.0, which retired celilo_contract 1.0. This module currently publishes 1.0, so any deploy fails at on_install:

Unsupported celilo_contract version '1.0'. Supported: 2.0

Audited before bumping, because the v2 break is behavioural rather than a signature change: it removed the hook return-value persistence channel, so a hook that returned state for celilo to save now has it silently dropped, with the deploy still reporting success.

Nothing here uses that channel:

hook shape verdict
on_install Promise<void> safe
register_forge Promise<void> safe
health_check returns its verdict object safe — v2 still consumes this

So the bump is safe on its own. Two lines: celilo_contract: "2.0" and version: 0.2.1 → 0.2.2 (manifest content changed; with no pending changesets the release workflow publishes the manifest as-is).

For contrast, lunacycle was not safe — its on_install minted an authentik token and returned it for persistence, which 2.0 drops silently. That is exactly why each module gets an audit rather than a blanket bump.

Part of the fleet-wide migration tracked in celilo#1419 and bead ce-h2w0.

celilo-mgr runs CLI 5.1.0, which retired `celilo_contract` 1.0. This module currently publishes 1.0, so any deploy fails at `on_install`: ``` Unsupported celilo_contract version '1.0'. Supported: 2.0 ``` **Audited before bumping**, because the v2 break is behavioural rather than a signature change: it removed the hook return-value persistence channel, so a hook that returned state for celilo to save now has it silently dropped, with the deploy still reporting success. Nothing here uses that channel: | hook | shape | verdict | |---|---|---| | `on_install` | `Promise<void>` | safe | | `register_forge` | `Promise<void>` | safe | | `health_check` | returns its verdict object | safe — v2 still consumes this | So the bump is safe on its own. Two lines: `celilo_contract: "2.0"` and `version: 0.2.1 → 0.2.2` (manifest content changed; with no pending changesets the release workflow publishes the manifest as-is). For contrast, `lunacycle` was **not** safe — its `on_install` minted an authentik token and returned it for persistence, which 2.0 drops silently. That is exactly why each module gets an audit rather than a blanket bump. Part of the fleet-wide migration tracked in celilo#1419 and bead `ce-h2w0`. 
celilo-mgr runs CLI 5.1.0, which retired celilo_contract 1.0, so this module
is currently undeployable — any deploy fails at on_install with 'Unsupported
celilo_contract version 1.0. Supported: 2.0'.

Audited before bumping, because the break is behavioural rather than a
signature change: v2 removed the hook return-value persistence channel, so a
hook that returned state for celilo to save now has it silently dropped.
Nothing here uses it — on_install and register_forge are Promise<void>, and
health_check's returns are its verdict, which v2 still consumes. So the bump
is safe on its own.

Version 0.2.1 -> 0.2.2 because manifest content changed; with no pending
changesets the release workflow publishes the manifest as-is.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
celilo/homepage!6
No description provided.