New release v1.0.10: GitHub Actions deployment and reliable recovery

We are pleased to announce microfeed v1.0.10, which adds a manual GitHub Actions deployment path with browser-approved Cloudflare access and makes setup recovery more reliable.

You can now choose the deployment environment that fits you best: ask a local AI coding agent to guide the process, run the same guarded deployment engine on GitHub's Ubuntu runner, or use the CLI directly.

Deploy from GitHub Actions

Fork the microfeed repository, add four repository secrets for the Cloudflare account ID, Worker name, administrator email, and Admin password, then manually run Create or update microfeed from a trusted branch. The workflow defaults to creating a new instance and can also update an existing Worker.

The workflow never runs automatically on a push, pull request, or schedule. It opens Cloudflare's browser authorization for each run instead of asking you to create and copy a long-lived Cloudflare API token. Wrangler credentials and microfeed connection state remain temporary and are removed when the job finishes.

The account-ID secret pins every management command to the intended Cloudflare account. If another person sees and consumes the temporary device code first, the run fails; authorization for a different account is rejected before Cloudflare resources are changed. After deployment, the workflow summary keeps the verified Site and Admin links easy to find.

See the GitHub Actions installation guide for the complete setup and safety details.

Resume an interrupted first deployment

Version 1.0.10 recognizes saved initialization state where the D1 database and R2 bucket already exist but the first Worker deployment did not finish. Running manage deploy now includes the original upload-signing secret and safely resumes the first deployment instead of requiring initialization to start over.

Completed deployments are unchanged. Existing secrets are not regenerated or rotated.

More reliable Windows deployment

The source-code-free launcher now supports cases where its private source cache and saved microfeed state live on different Windows drives. It stages a short-lived Wrangler configuration beside the repository when required by Astro and Cloudflare's Vite integration, then removes it when the command exits.

The launcher also verifies critical JavaScript entry points after installing its private workspace. If the cached dependency tree is incomplete, it performs one clean repair before continuing. Spaces, Unicode paths, cross-drive local development, and both x64 Windows and Windows 11 ARM runners are covered by automated tests.

Install or update microfeed

The recommended path is to open an AI coding agent that can run local shell commands and ask:

Run `npx @microfeed/cli@1.0.10 manage` and follow every instruction it prints until `status` verifies the deployment.

The launcher requires Node.js 22.12 or newer and npm. It does not require Git or Corepack. Complete browser authorization handoffs when prompted, but never paste a Cloudflare token, password, or private password-setup link into the conversation.

If you prefer a hosted environment, follow the GitHub Actions guide. If you maintain a cloned or modified source tree, follow the manual update guide and use yarn manage.

Published packages

Both @microfeed/cli@1.0.10 and @microfeed/theme-kit@1.0.10 are available from npm.

For this release, use yarn dlx @microfeed/theme-kit@1.0.10 ... as documented. On macOS and Linux, invoking the theme-kit or microfeed-theme executable through an npm-installed POSIX bin symlink may exit without output. This limitation does not affect @microfeed/cli or Windows deployment.

Read the complete v1.0.10 release notes, or see the full changelog for every change.