Releases on crofty

crofty 0.21.0 — crofty update, in place

Tue, 21 Jul 2026 22:15:00 +0900

Until now, moving to a new crofty meant going back to the installer. crofty update fetches the latest release and swaps it for the crofty you’re running, without leaving the terminal.

`crofty update`

Run it and it fetches the latest release and replaces the running crofty with it. On the installer routes it updates the bundled Hugo alongside it.

If you’re already on the latest, it says so and changes nothing.

crofty 0.20.0 — sites with a worker deploy now

Tue, 21 Jul 2026 00:08:00 +0900

If one contact form was the reason your whole site went out through another tool, that reason is gone. crofty deploy now carries a _worker.js instead of stopping at it.

What used to happen

A project with a _worker.js at its root was refused. crofty deploys to Cloudflare Pages, and a static-only upload would have replaced whatever was answering those routes — so the form kept its URL and quietly stopped working.

crofty 0.18.0 — two ways in

Fri, 10 Jul 2026 12:35:00 +0900

crofty used to arrive six ways. Every one of them did the same thing — copy a single binary onto your PATH — and most of them existed for a second reason: to drag Hugo in as a package dependency. The click installers carry Hugo themselves now, which retires that reason. 0.18.0 removes what was left.

Before

brew install ShiroDoromoto/crofty/crofty
scoop install crofty
sudo apt install crofty      # from a repo that made you write trusted=yes
sudo dnf install crofty      # …and gpgcheck=0
curl -fsSL https://crofty.site/install.sh | sh

After

crofty.pkg / crofty-setup.exe    # double-click; Hugo is inside
curl -fsSL https://crofty.site/install.sh | sh

Or download the archive from the releases page and put the binary wherever you like. That route needs nothing but a browser, which matters more than it sounds: on some Windows machines the system TLS stack refuses the one-liner outright.

crofty 0.17.0 — a local preview that can't linger

Tue, 07 Jul 2026 12:50:00 +0900

crofty preview wraps a blocking hugo server so you can see your site in a browser. Press Control-C and it stops. But when an AI backgrounds it to keep working, there’s no Control-C to press — so the server just keeps running.

0.17.0 gives preview a lifecycle anyone (or any agent) can drive from a separate process, without changing the foreground Control-C experience.

Before

A backgrounded preview had no off switch. Nothing recorded that it was running, so a second process couldn’t find it, couldn’t tell whether one was up, and couldn’t stop it. It lingered until the machine went down.

crofty 0.16.0 — catch a theme cache that git would commit

Sat, 20 Jun 2026 12:25:00 +0900

crofty regenerates its theme under .crofty/themes/ on every build. If git tracks that folder, it gets committed and churns your history each time you build.

Before

The build hinted about .gitignore only when the file was missing entirely. A site that had a .gitignore without the /.crofty/themes/ rule was missed — so the regenerated theme kept getting committed with no warning.

After

crofty build now asks git what it actually ignores, not just whether a .gitignore exists, and tells you what to do:

crofty 0.15.0 — a .gitignore on init, and a nudge for sites that lack one

Sat, 20 Jun 2026 12:10:00 +0900

A crofty site that you put under git init would commit things it shouldn’t: the built dist/, Hugo’s working dirs, and the theme cache crofty regenerates on every build.

Before

crofty init left it to you to write a .gitignore. If you forgot, the build output and the regenerated theme rode along into every commit.

After

crofty init now writes a minimal .gitignore for a fresh site. It ignores what crofty rebuilds — /dist/, /public/, /resources/, and /.crofty/themes/ — while keeping .crofty/config.json tracked, because the build needs it and it holds no secrets. An existing .gitignore (possible with crofty init .) is left untouched.

crofty 0.13.0 — clearer messages when analytics returns a 403

Thu, 18 Jun 2026 11:00:00 +0900

When crofty analytics got a 403 reading GA4 or Search Console, it didn’t say enough about which kind of error it was.

Before

It only said “grant access”.

After

It now names both possible causes:

a wrong (or non-existent) property id
the service account lacking access

On top of that, it prints Google’s own error message verbatim. For an AI, it returns a structured error under --json (cause, the property tried, a suggested next step).

crofty 0.12.0 — SFTP deploys no longer stall on the host-key prompt

Thu, 18 Jun 2026 01:00:00 +0900

A crofty deploy over SFTP froze at the prompt that asks you to trust a server’s host key the first time crofty sees it.

Before

crofty looked only at its own record of known servers (empty to start), so a server you’d reached over ssh/sftp many times was still treated as new and stopped to ask — freezing the deploy.

After

crofty now reads your ~/.ssh/known_hosts (read-only). A server you already trust just deploys.
For a genuinely new host, crofty deploy --yes accepts its key without the y/N prompt — for when an AI assistant is driving and no one’s at the keyboard (crofty agent lists --yes).

A host key that changes after it was first trusted is still a hard error.

crofty 0.11.0 — apt & dnf on Linux, and an update notice

Thu, 18 Jun 2026 00:00:00 +0900

On Linux, installing and updating crofty was manual, and it was easy to miss a newer release.

Before

Linux meant downloading a .deb/.rpm and installing it by hand — and updating meant doing it again.
Package managers don’t silently upgrade a tool, so it was easy to sit on an old build and miss a fix.

After

A hosted apt/dnf repo: one line to install, and apt upgrade / dnf update keeps it current with the rest of your system.
After a command, crofty prints a one-line update hint when a newer release is out. It’s quiet (once a day, interactive only), never updates itself, and is off with CROFTY_NO_UPDATE_CHECK=1. crofty agent --json carries updateAvailable so your assistant sees it too.

# Debian/Ubuntu
echo "deb [trusted=yes] https://apt.fury.io/shirodoromoto/ * *" | sudo tee /etc/apt/sources.list.d/crofty.list
sudo apt update && sudo apt install crofty

# Fedora/RHEL
sudo tee /etc/yum.repos.d/crofty.repo >/dev/null <<'EOF'
[crofty]
name=crofty
baseurl=https://yum.fury.io/shirodoromoto/
enabled=1
gpgcheck=0
EOF
sudo dnf install crofty

crofty 0.9.0 — read GA4 / Search Console with crofty analytics

Wed, 17 Jun 2026 14:30:00 +0900

Reading your own traffic meant opening a dashboard.

Before

There was no way to read your GA4 or Search Console data from crofty.

After

crofty analytics reads it from the command line — as a plain table, or as JSON for your AI to parse.

crofty analytics ga4 top-pages          # GA4: visitors, pages, sources…
crofty analytics search queries         # Search Console: queries, pages, sitemaps
crofty analytics ga4 top-pages --json   # machine-readable, for an assistant

It uses your own Google service-account key (kept in your OS keychain, talking to Google directly). Set it up once with crofty analytics connect --key <file>; crofty analytics status tells you any missing step.

crofty 0.6.0 — deploy over SFTP and FTPS

Tue, 16 Jun 2026 16:00:00 +0900

crofty deploy could only target Cloudflare Pages.

Before

deploy meant Cloudflare Pages and nothing else.

After

The same built site can go to your own VPS over SFTP or to shared hosting over FTPS. You pick the target when you set the project up.

crofty init --provider sftp --host example.com --user me --path /var/www/site
crofty init --provider ftps --host example.com --user me --path /public_html

crofty deploy uploads dist/ there (the password is kept in your OS keychain). Cloudflare Pages stays the default. Plain FTP isn’t supported, and --path is your web root, not your login home.

crofty 0.5.0 — Linux packages (.deb / .rpm)

Tue, 16 Jun 2026 00:00:00 +0900

crofty was macOS (Homebrew) and Windows (Scoop) only — there was no official Linux package.

Before

There were no official Linux packages.

After

crofty ships .deb and .rpm builds (amd64 and arm64) on the GitHub releases.

sudo dpkg -i crofty_*_linux_amd64.deb   # Debian/Ubuntu
sudo rpm -i crofty_*_linux_amd64.rpm    # Fedora/RHEL

The package only recommends Hugo, so install hugo-extended yourself.

crofty 0.1.0 — the first public release

Mon, 15 Jun 2026 19:00:00 +0900

crofty’s first public release. Write Markdown, publish a site you own — no account here, nothing kept. Installable via Homebrew and Scoop.

# macOS
brew install ShiroDoromoto/crofty/crofty
# Windows
scoop bucket add crofty https://github.com/ShiroDoromoto/scoop-crofty
scoop install crofty

Then follow Get started.