v0.1.8

Everything since v0.1.7. This release moves rsync.ai to the rsync.ai Source-Available License, and calls the product rsync.ai everywhere: the repository is now rsync-ai/rsync.ai, and the Docker containers, the Kubernetes release and the MCP server carry the name. It adds no features.
Images are published for linux/amd64 and linux/arm64.

Install

Docker (Compose)

curl -sSL https://raw.githubusercontent.com/rsync-ai/rsync.ai/v0.1.8/install.sh | bash

Re-running it on an existing install upgrades it to v0.1.8. The containers are now named rsync-ai-*; your data is in volumes, which keep their names, and the upgrade replaces each container under its new name.

Kubernetes (Helm): one command. It sizes the install to your cluster. For this release, pass the chart version:

curl -sSL https://raw.githubusercontent.com/rsync-ai/rsync.ai/v0.1.8/install-k8s.sh | RSYNC_CHART_VERSION=0.1.8 bash

Without RSYNC_CHART_VERSION=0.1.8, the v0.1.8 script still installs chart 0.1.7. A follow-up change moves the script's default to 0.1.8.

You can also pull the chart directly: helm pull oci://ghcr.io/rsync-ai/charts/rsync-ai --version 0.1.8.

License

• New license: the rsync.ai Source-Available License v1.0 (LICENSE), replacing the Elastic License 2.0 from this release on. Running rsync.ai for your own business, and for personal or non-commercial projects, stays free. Without a separate agreement you may not sell it, host it for others, embed it in a product you sell, build a competing product from it, or share copies except free of charge for non-commercial purposes.
• Releases up to and including v0.1.7 stay under the Elastic License 2.0. Its text is kept in LICENSES/.
• Contributions now need a signed CLA, once, in addition to the DCO sign-off.
• Every connector's license field carries the new license's identifier, LicenseRef-rsync.ai-SAL-1.0, instead of MIT or ELv2.

Named rsync.ai, not rsync

rsync is also the name of a file-copy tool that has existed for decades. The product is rsync.ai, and the names below now say so.

• The repository is github.com/rsync-ai/rsync.ai. A clone lands in rsync.ai/. GitHub redirects the old web, git and raw addresses, so an install command that names rsync-ai/rsync still works.
• Docker: the self-host containers are named rsync-ai-* (rsync-ai-postgres, rsync-ai-orchestrator, ...). Scripts that call docker exec or docker logs with an old name need the new one.
• Kubernetes: the default release and namespace are rsync-ai, so resources are named rsync-ai-frontend, rsync-ai-secrets and so on. install-k8s.sh finds an install under the old default (rsync in rsync) and upgrades it in place. If you run helm yourself, keep upgrading under the name you installed with.
• AI clients: the setup snippets name the MCP server rsync-ai, and the server reports rsync.ai as its title. A client you already set up keeps working under the name you gave it.
• Load test: RSYNC_AI_EMAIL and RSYNC_AI_PASSWORD replace RSYNC_EMAIL and RSYNC_PASSWORD in scripts/loadtest.
• Settings (RSYNC_*), Kafka topics (rsync.*), the rsync-network Docker network and ai.rsync.* labels keep their names.

Removed

• The petstore example connector, a demo of a generated REST connector, and its OAuth provider entry.

Tested before release

This release changes names, wording and the license, not pipeline behaviour. It was checked by the test suites, not by a live install:

• The repository's CI on the release commit, and locally: the documentation and license guards, the installer tests, the Go packages and frontend tests the change touched.
• install-k8s.sh's in-place upgrade from the old default release name is covered by tests run against a real helm v3.16.4, not by an upgrade on a live cluster.
• A Docker upgrade from v0.1.7, which renames every container, was not run on a live install.