Skip to content
Early bird + Black Friday · 73% off

Get ZeroDirs for $179 $49

Claim $49 deal

Updates

You own the source, so an update is something you pull. This page is about what that costs.

CHANGELOG.md in the starter follows Keep a Changelog. The version is also in package.json.

Semantic versioning, read as it applies to a codebase you own rather than a library you install:

Means
Major a change that will not merge cleanly into a customised copy, or that changes the shape of site.config.ts
Minor new features and new config fields, with defaults that keep an existing site building
Patch fixes and documentation

Every optional block in site.config.ts has a default, and a fresh clone parses with all of them missing, so a minor release that adds a field never breaks your build.

No release edits these:

  • site.config.ts
  • src/content/
  • public/

Everything else — templates, library modules, integrations, tests — is where an update lands, and where you resolve a conflict if you edited it. The changelog names structural changes before you pull.

Your access to zerodirs/zerodirs is read-only. Commit your own work in your own repository and pull ours into it.

  1. Read the entry first. CHANGELOG.md — also on this site as Changelog — names every structural change under Changed and Removed. Those are the only places a merge conflict can come from.

  2. Pull. If your copy still has the starter as origin:

    Terminal window
    git pull origin main

    If you pushed your copy to a repository of your own, add the starter once as a second remote and merge from it:

    Terminal window
    git remote add upstream git@github.com:zerodirs/zerodirs.git # once
    git fetch upstream
    git merge upstream/main

    A conflict in site.config.ts, src/content/ or public/ means the merge is wrong, not the release.

  3. Install and migrate.

    Terminal window
    pnpm install
    pnpm db:migrate:local # only when the entry says the release ships a migration

    Migrations are expand-only, so an older Worker keeps working against a newer database and pnpm db:migrate:remote can run before the deploy.

  4. Verify, then deploy.

    Terminal window
    pnpm check
    pnpm test
    pnpm build

    The build is the one that matters: only a full build exercises the route table, the file budget, the sitemap and the orphan check together. Then push to main, or pnpm deploy — see Deploy on git push.

Quote the version from CHANGELOG.md and paste the full output of the failing command, including the lines above the error. Most build failures in this project name a field path or a file, and that line is usually the whole diagnosis.