Skip to content
BUILD.
← All guides

Upgrade guide · 7 min read

Upgrade to Build 1.1

Preserve your projects and configuration, apply the update, and verify shared editing before your team resumes.

Applies to Build 1.1.0 · Updated September 15, 2026

Download this guide (.md)

1. Stop editing and keep a backup

Keep your existing installation and original ZIP. Finish active builds before making a backup. For local installations, stop the server and preserve .wrangler state, .build-local data, private environment files, and custom configuration.

For hosted Agency, back up D1, retain the old Worker version, and record your rollback procedure. Keep backups private and verify you can restore them.

2. Extract the new download separately

Open Your download above and get Build 1.1.0. Extract it separately. Read docs/UPGRADE-1.1.md before merging it into a staged copy of your installation. Preserve your custom source, existing data, resource IDs and encryption/signing keys.

The new package reports 1.1.0. The original Build 1.0.0 ZIP inherited an upstream package version of 1.5.0; use the ZIP label and release notes to distinguish that older download.

Run in your Build folder
node -p "require('./package.json').version"

3a. Update a local Personal installation

Run these from the staged installation after merging the new source and locked dependencies. The installer applies pending local migrations. Confirm an existing project still opens and exports. Personal remains a single-user workflow.

Run in your Build folder
node scripts/install.mjs --profile personal --yes --no-start --json
bun run doctor -- --json
bun run dev:local

3b. Update a hosted Agency installation

Keep your existing Clerk application, Cloudflare resource configuration and private agency settings. Review the plan, then follow the apply procedure in docs/RELEASE.md. An existing operator does not need first-install --bootstrap.

The remote deployment must apply migration 0012_build_shared_projects.sql before publishing the matching server and frontend. Running the local installer does not migrate a remote database. Downloading a ZIP or editing an environment file does not update an already-running deployment.

Run in your Build folder
PUPPETEER_SKIP_DOWNLOAD=true bun install --frozen-lockfile
bun run deploy -- --plan --config wrangler.production.jsonc --env-file .build-local/install/agency.env

4. Test with two accounts

  1. Confirm an existing project is still private.
  2. Share a disposable hosted full-stack project as its creator.
  3. Finish editing and have the second member take control.
  4. Make a small build or edit, check the preview, and export source.
  5. Confirm the previous editor cannot write while the teammate has control.
  6. As the creator, make it private after operations finish. Verify the teammate loses access.
Shared previews omit personal Environment bindings. Use a harmless dummy value to verify this behavior. The upgrade does not establish the cause of an existing Clerk sign-in loop.

If a check fails

Pause team access, preserve the failing state and record the exact step. Follow the rollback plan from your backup. Migration 0012 is additive; do not drop its table as an improvised rollback.

Returning to 1.0.0 code removes shared editing. Review the old Worker and database backup together, including changes since the backup, before restoring data.

Keep going