From 2fbfbb6bc5c53dc063db06f430683c2786471b01 Mon Sep 17 00:00:00 2001 From: Collin Rijock Date: Thu, 29 Oct 2026 18:55:15 +0000 Subject: [PATCH 1/2] copper-cloud 0.12.0: sync document revisions (#7) --- Cargo.lock | 2 +- Cargo.toml | 2 +- README.md | 4 ++-- docs/install.md | 4 ++-- docs/v0.12.0.md | 18 ++++++++++++++++++ 5 files changed, 24 insertions(+), 6 deletions(-) create mode 100644 docs/v0.12.0.md diff --git a/Cargo.lock b/Cargo.lock index 76292ec..18cf905 100644 --- a/Cargo.lock +++ b/Cargo.lock @@ -638,7 +638,7 @@ checksum = "a6ef517f0926dd24a1582492c791b6a4818a4d94e789a334894aa15b0d12f55c" [[package]] name = "copper-cloud" -version = "0.11.1" +version = "0.12.0" dependencies = [ "anyhow", "axum", diff --git a/Cargo.toml b/Cargo.toml index 44333fb..ea856cd 100644 --- a/Cargo.toml +++ b/Cargo.toml @@ -8,7 +8,7 @@ members = [ ] [workspace.package] -version = "0.11.1" +version = "0.12.0" edition = "2021" license = "MIT" repository = "https://github.com/copper-browser/copper-cloud" diff --git a/README.md b/README.md index 40bbbb3..faf7690 100644 --- a/README.md +++ b/README.md @@ -33,7 +33,7 @@ curl -fsSL https://raw.githubusercontent.com/copper-browser/copper-cloud/main/in or from a release tarball: ```sh -tar xzf copper-cloud-0.11.1-linux-x86_64.tar.gz && sudo ./install.sh +tar xzf copper-cloud-0.12.0-linux-x86_64.tar.gz && sudo ./install.sh ``` The installer sets up Postgres (unless you pass `DATABASE_URL`), a `copper-cloud` system user, @@ -147,7 +147,7 @@ All commands take `--config PATH` (default `/etc/copper-cloud/copper-cloud.toml` - [Operations](docs/operations.md) — doctor, logs, metrics, backups, upgrades - [Onboarding a team](docs/onboarding.md) — single sign-on first, link codes, people, keeping links valid - [Single sign-on + agent integrations](docs/sso.md) — Google / OIDC setup, `/start`, agent pairing -- [v0.11.1 release notes](docs/v0.11.1.md) · [v0.11.0](docs/v0.11.0.md) · [v0.10.0](docs/v0.10.0.md) · [v0.9.0](docs/v0.9.0.md) · [v0.8.1](docs/v0.8.1.md) · [v0.8.0](docs/v0.8.0.md) · [v0.7.0](docs/v0.7.0.md) · [v0.6.0](docs/v0.6.0.md) · [v0.5.0](docs/v0.5.0.md) · [v0.4.0](docs/v0.4.0.md) · [v0.3.0](docs/v0.3.0.md) +- [v0.12.0 release notes](docs/v0.12.0.md) · [v0.11.1](docs/v0.11.1.md) · [v0.11.0](docs/v0.11.0.md) · [v0.10.0](docs/v0.10.0.md) · [v0.9.0](docs/v0.9.0.md) · [v0.8.1](docs/v0.8.1.md) · [v0.8.0](docs/v0.8.0.md) · [v0.7.0](docs/v0.7.0.md) · [v0.6.0](docs/v0.6.0.md) · [v0.5.0](docs/v0.5.0.md) · [v0.4.0](docs/v0.4.0.md) · [v0.3.0](docs/v0.3.0.md) ## Development diff --git a/docs/install.md b/docs/install.md index 022907a..807adbc 100644 --- a/docs/install.md +++ b/docs/install.md @@ -12,7 +12,7 @@ curl -fsSL https://raw.githubusercontent.com/copper-browser/copper-cloud/main/in From a release tarball (files at the archive root): ```sh -tar xzf copper-cloud-0.11.1-linux-aarch64.tar.gz +tar xzf copper-cloud-0.12.0-linux-aarch64.tar.gz sudo ./install.sh ``` @@ -67,7 +67,7 @@ data stay. | `COPPER_CLOUD_MASTER_KEY` | generated | base64url of exactly 32 bytes | | `COPPER_CLOUD_BINARY` | — | local binary or release tarball | | `COPPER_CLOUD_BINARY_URL` | — | URL of a binary or release tarball | -| `COPPER_CLOUD_VERSION` | `latest` | GitHub release to fetch (e.g. `0.11.1`) | +| `COPPER_CLOUD_VERSION` | `latest` | GitHub release to fetch (e.g. `0.12.0`) | | `GITHUB_TOKEN` | — | for a private GitHub repository | `sudo -E` (or `sudo VAR=… sh install.sh`) is needed to pass variables through sudo. diff --git a/docs/v0.12.0.md b/docs/v0.12.0.md new file mode 100644 index 0000000..b7808bb --- /dev/null +++ b/docs/v0.12.0.md @@ -0,0 +1,18 @@ +# copper-cloud v0.12.0 + +Sync documents can be put back. One new migration (`0015_sync_doc_revisions`); an upgrade from +0.11.x is a binary swap (`sudo ./install.sh` from the tarball) and the server migrates on start. + +- **Revisions of every sync document** ([api.md](api.md)). Before a `spaces`, `settings`, + `bookmarks` or `tabs:` document is overwritten, the version it replaces is kept + (still encrypted) with the device that wrote it and its build. The last 20 per document are + kept. `GET /v1/sync/docs/{domain}/revisions` lists them, `GET …/revisions/{version}` returns + one, and `POST …/revisions/{version}/restore` writes it back as a new version, so every + device pulls it. `/v1/info` lists `doc_revisions`. +- **`X-Copper-Build`.** Coppers may send their build with a write; it is stored beside the + document and its revisions. Optional: older Coppers sync as before. +- **`copper-cloud admin docs revisions|restore --user --domain [--version]`** for the operator. + +Why: a device whose state had drifted overwrote a user's folders on every Mac, and there was no +earlier version to go back to (Copper 1.0.20261029.95, copper-linux 0.5.1 and copper-windows +0.2.1 stop the overwrite itself). From 8a57623eff7e9f5d4aef782cf9475574538357d1 Mon Sep 17 00:00:00 2001 From: Collin Rijock Date: Thu, 29 Oct 2026 18:58:05 +0000 Subject: [PATCH 2/2] Cargo.lock: workspace crates at 0.12.0 --- Cargo.lock | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Cargo.lock b/Cargo.lock index 18cf905..3e1c5c5 100644 --- a/Cargo.lock +++ b/Cargo.lock @@ -669,7 +669,7 @@ dependencies = [ [[package]] name = "copper-cloud-canvas-link" -version = "0.11.1" +version = "0.12.0" dependencies = [ "anyhow", "axum", @@ -698,7 +698,7 @@ dependencies = [ [[package]] name = "copper-cloud-canvas-migrate" -version = "0.11.1" +version = "0.12.0" dependencies = [ "anyhow", "axum", @@ -722,7 +722,7 @@ dependencies = [ [[package]] name = "copper-cloud-core" -version = "0.11.1" +version = "0.12.0" dependencies = [ "aes-gcm", "anyhow",