Bump @celilo/capabilities to ^2.0.0 (celilo v1.0.0) #1

Merged

forgejo-admin merged 1 commit from caps2-homepage into main

2026-08-17 22:03:30 +00:00

forgejo-admin commented

2026-08-17 21:31:11 +00:00

Owner

celilo v1.0.0 shipped @celilo/capabilities@2.0.0, a breaking capability release. This module was pinned to ^0.9.1.

What changed upstream

Withdrawal moved from the consumer to the provider. Removing a module now dispatches a new on_consumer_removed hook to every provider of every capability the departing module declared, and each provider withdraws what it minted. That deleted the consumer-facing methods:

PublicWebCapability.unregister_routes
PrivateWebCapability.unregisterRoutes
FirewallCapability.unexposeService / withdrawTrustedSource
RegisterTrustedSourceRequest.subnet → subnets: string[]
IssueRunnerTokenRequest gains a required runnerName
PortForward gains registeredBy

Impact here: none on the hooks

peterbanka-org is a pure consumer (public_web, dns_registrar, and optionally source_forge / registry_publish) and provides no capability, so nothing withdraws and it never implemented on_consumer_removed. It calls none of the removed methods. The hook scripts are unchanged.

The pin still has to move: a module runs the capability code it bundles, not the management server's install (celilo#173).

Verification

tsc --noEmit -p celilo-module/scripts/tsconfig.json — clean against the 2.0.0 type surface.
Gate proven, not assumed: adding a call to the removed unregisterRoutes fails with TS2551: Property 'unregisterRoutes' does not exist on type 'PublicWebCapability'; removing it returns to clean.
celilo module check ./celilo-module (CLI 1.0.0) — 7 ok, 0 fail. public_web@3.1.0 and dns_registrar@4.0.0 both satisfiable.
astro check — 0 errors, 0 warnings.

Version

0.1.0 → 0.2.0, stamped by celilo module version from changesets (version_source: kind: changeset; the manifest line is not hand-edited). My changeset declared patch — a dependency re-pin with no behavior change. The minor comes from the changeset that had been pending since 0be59b3.

🤖 Generated with Claude Code

celilo v1.0.0 shipped `@celilo/capabilities@2.0.0`, a breaking capability release. This module was pinned to `^0.9.1`. ## What changed upstream Withdrawal moved from the consumer to the provider. Removing a module now dispatches a new `on_consumer_removed` hook to every provider of every capability the departing module declared, and each provider withdraws what it minted. That deleted the consumer-facing methods: - `PublicWebCapability.unregister_routes` - `PrivateWebCapability.unregisterRoutes` - `FirewallCapability.unexposeService` / `withdrawTrustedSource` - `RegisterTrustedSourceRequest.subnet` → `subnets: string[]` - `IssueRunnerTokenRequest` gains a required `runnerName` - `PortForward` gains `registeredBy` ## Impact here: none on the hooks `peterbanka-org` is a pure consumer (`public_web`, `dns_registrar`, and optionally `source_forge` / `registry_publish`) and provides no capability, so nothing withdraws and it never implemented `on_consumer_removed`. It calls none of the removed methods. The hook scripts are unchanged. The pin still has to move: a module runs the capability code it **bundles**, not the management server's install (celilo#173). ## Verification - `tsc --noEmit -p celilo-module/scripts/tsconfig.json` — clean against the 2.0.0 type surface. - Gate proven, not assumed: adding a call to the removed `unregisterRoutes` fails with `TS2551: Property 'unregisterRoutes' does not exist on type 'PublicWebCapability'`; removing it returns to clean. - `celilo module check ./celilo-module` (CLI 1.0.0) — 7 ok, 0 fail. `public_web@3.1.0` and `dns_registrar@4.0.0` both satisfiable. - `astro check` — 0 errors, 0 warnings. ## Version 0.1.0 → 0.2.0, stamped by `celilo module version` from changesets (`version_source: kind: changeset`; the manifest line is not hand-edited). My changeset declared **patch** — a dependency re-pin with no behavior change. The **minor** comes from the changeset that had been pending since 0be59b3. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

forgejo-admin added 1 commit

2026-08-17 21:31:11 +00:00

Bump @celilo/capabilities to ^2.0.0 (celilo v1.0.0) 356a167b6c

celilo v1.0.0 moves capability withdrawal from the consumer to the
provider: removing a module now dispatches on_consumer_removed to every
provider of every capability the departing module declared, and each
provider withdraws what it minted. That deleted the consumer-side
withdrawal methods (unregister_routes, unregisterRoutes,
unexposeService, withdrawTrustedSource) and reshaped
RegisterTrustedSourceRequest, IssueRunnerTokenRequest and PortForward.

This module calls none of the removed methods and provides no
capability, so nothing withdraws and no hook changes. The pin and the
bundled copy still have to move, because a module runs the capability
code it BUNDLES, not the management server's install (celilo#173).

  tsc --noEmit                clean against the 2.0.0 surface
  celilo module check         7 ok, 0 fail

Version stamped 0.1.0 -> 0.2.0 by `celilo module version`. My changeset
declared patch; the minor comes from the changeset already pending since
0be59b3.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

forgejo-admin referenced this pull request

2026-08-17 21:33:13 +00:00

bun run lint:css hangs forever (lasertag check never returns) #2

forgejo-admin merged commit 6124840434 into main

2026-08-17 22:03:30 +00:00

forgejo-admin referenced this pull request from a commit

2026-08-17 22:03:31 +00:00

Merge pull request 'Bump @celilo/capabilities to ^2.0.0 (celilo v1.0.0)' (#1) from caps2-homepage into main