New release v1.0.8: Clone-free deployment on Windows

We are pleased to announce microfeed v1.0.8, which makes the published deployment launcher self-contained and brings the clone-free workflow to Windows.

People and coding agents can now deploy or update microfeed from any folder with Node.js and npm. There is no need to maintain a Git checkout or install Corepack, and Windows ARM computers are supported by running the x64 build of Node.js through Windows application emulation.

Deploy without a source checkout

The official @microfeed/cli@1.0.8 package now bundles the exact microfeed 1.0.8 deployment runtime and its pinned Yarn release. The launcher prepares and reuses a private deployment workspace while keeping replaceable source cache separate from saved instance configuration and deployment state.

Run the complete management interface from any working folder:

npx @microfeed/cli@1.0.8 manage

The launcher requires Node.js 22.12 or newer and npm. Git and Corepack are no longer required for this published workflow. Account discovery, initialization, connection, deployment, status, local development, themes, snapshots, domains, authentication, and guarded destruction remain available through the same manage command.

Reliable process launching on Windows

Version 1.0.8 runs packaged TypeScript, Wrangler, Yarn, npm, and npx JavaScript entry points directly with Node instead of invoking Windows command shims. This preserves arguments and platform-correct paths when working folders contain spaces or non-ASCII characters and when a source checkout uses CRLF line endings.

The release also keeps local development attached to the management process and passes Wrangler configuration through Windows-safe paths. The complete launcher and Worker runtime are tested in continuous integration on both windows-latest and Windows 11 ARM runners using x64 Node.js.

Use x64 Node.js on every Windows computer

Cloudflare's local runtime does not currently provide a native Windows ARM64 executable, so microfeed management on Windows requires the x64 build of Node.js. This applies to both x64 Windows computers and Windows ARM computers, where x64 Node.js runs through the operating system's application emulation.

Before starting, verify the active architecture:

node -p "process.arch"

The command must print x64. If it prints arm64, install the x64 Windows build from nodejs.org, open a new terminal, verify the architecture again, and rerun the same microfeed command.

Update an existing deployment

Open an AI coding agent that can run local shell commands and ask:

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

Complete Cloudflare browser-authorization handoffs when prompted, but never paste a Cloudflare token, password, or private password-setup link into the conversation.

If the intended instance is already saved and unambiguous, the equivalent direct commands are:

npx @microfeed/cli@1.0.8 manage deploy --instance <instance-name>

npx @microfeed/cli@1.0.8 manage status --instance <instance-name>

See the update guide, AI-agent deployment guide, and manage CLI reference for the complete workflow.

Published packages

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

For this release, use yarn dlx @microfeed/theme-kit@1.0.8 ... as documented. On macOS and Linux, invoking the theme-kit 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.8 release notes, or see the full changelog for every change.