New release v1.0.5: Webhooks and content automation

We are pleased to announce microfeed v1.0.5, an update focused on signed webhooks and content automation.

microfeed 1.0.5 adds opt-in, cost-bounded webhook delivery through Cloudflare Queues, exact event contracts, Admin and CLI testing tools, and guarded infrastructure lifecycle controls. It also improves the public Default theme, Admin collection loading, theme asset delivery, bundled-theme maintenance, and coding-agent guidance.

Signed, cost-bounded webhooks

Webhooks let an integration react when content changes without polling. Version 1.0.5 provides 22 versioned channel, item, Page, Site File, theme, and webhook events. Every delivery uses Standard Webhooks headers and a unique encrypted signing secret for its endpoint.

Content mutations and their matching webhook outbox records are committed atomically in D1, then delivered through a dedicated Cloudflare Queue. Delivery is at least once, with bounded retries, reconciliation, retention, and automatic endpoint pausing after repeated failures.

Administrators can configure up to 20 endpoints from Admin, choose the exact event subscriptions for each one, reveal or rotate its signing secret, disable or delete integrations, inspect delivery attempts, and manually redeliver an event. An owner-controlled UTC daily delivery budget provides a cost guard, while the Overview and Deliveries screens show usage, Queue-operation estimates, backlog, retries, alerts, and endpoint health.

Webhook events carry stable content snapshots plus explicit causation, correlation, idempotency, and test: true metadata. The generated OpenAPI document, interactive API reference, and self-contained llms-full.txt publish the exact webhook operation, event union, Standard Webhooks headers, schemas, and named examples.

Event Explorer and integration tooling

Admin now includes a Webhook Event Explorer. It can preview generated examples or current site content, display the exact Payload, Schema, and Headers, print a preview locally without side effects, or send a signed test through the normal delivery path.

The official @microfeed/cli adds webhook sample for exact contract examples, webhook scaffold for offline JavaScript and Python receiver starters, and webhook listen for inspecting or forwarding verified deliveries. The optional webhook listen --tunnel workflow receives tests from a deployed site through a temporary Cloudflare Quick Tunnel using a pinned, checksum-verified cloudflared binary.

Local yarn dev automatically provides isolated Queue, consumer, maintenance-trigger, and signing-secret simulation. It creates no Cloudflare resources and incurs no deployed Queue usage, so receivers and signed tests can be developed before production infrastructure is enabled.

The new content-automation documentation explains how the API, webhooks, and CLI work together. It includes n8n and Zapier guides, a no-code webhook testing path, production receiver guidance, automation examples, and coding-agent prompts grounded in each instance's generated contract.

Safe and reversible webhook infrastructure

Deployed webhooks remain explicitly opt-in. Production and preview use separate dedicated Queues, and enabling one environment does not enable the other. An ordinary deployment preserves the saved lifecycle state: enabled remains enabled, disabled remains detached, and never-provisioned remains off.

The new yarn manage deploy --disable-webhooks workflow pauses and purges the dedicated Queue, cancels pending deliveries, and removes producer, consumer, and Cron configuration while retaining the Queue identity, encrypted endpoint secrets, endpoint settings, and delivery history. Re-enabling later reuses those exact resources without replaying events from the disabled interval.

Enable, disable, status, connection, and destruction operations now verify the exact Queue identity and consumer, preflight Cloudflare authorization, retry one credential refresh when needed, preserve resumable transitions, and fail closed rather than changing an unexpected resource.

Publishing, Admin, and theme improvements

The bundled Default theme adds persistent System, Light, and Dark modes, improved desktop and mobile navigation, a more focused search experience, refined typography and rich-content spacing, and a better mobile layout.

Items, Pages, and Site Files now load through lightweight Admin shells and private summary endpoints. Filtering, sorting, and pagination update in place while retaining useful loading, stale-request cancellation, and retry states instead of performing a full route reload.

Immutable theme assets now use a configured R2 custom domain and Cloudflare CDN when available, with the existing same-origin /media/ route as a fallback. Deployment keeps the newest bundled Default-theme candidate available without forcing activation and safely prunes superseded inactive versions while preserving active, rollback, draft, origin, and asset references.

This release also expands Claude Code and coding-agent guidance across the application repository, theme starters, documentation, and agent workflows.

Updating an existing Workers deployment

If your local repository clone is already connected to a microfeed Worker, protect any local work, update the clone, and run:

yarn install --immutable
yarn manage deploy
yarn manage status

The deployment applies the webhook storage, named API-key scope, delivery-budget, and reversible-infrastructure migrations; reconciles bundled theme versions; runs project checks; builds and deploys the Worker; and verifies the result.

Ordinary updates do not enable webhooks on a site that has never provisioned them. Existing enabled or disabled state is preserved. After reviewing the additional Cloudflare resources and usage, enable an exact production site with:

yarn manage deploy --enable-webhooks --instance <instance-name>
yarn manage status --instance <instance-name>

You can also open the connected repository in a local coding agent and ask:

Deploy to Cloudflare.

See the update guide, webhook guide, content automation overview, and theme guide for details.

Version 1.0.5 makes microfeed ready for signed, event-driven integrations while keeping webhook infrastructure optional and owner-controlled. See the full changelog for every change.