v3.0.0

Collattice v3.0.0

Collaboard is now Collattice.

The project has been renamed following a trademark concern regarding the previous name. This is a naming/branding change; the project itself continues as before.

"Collattice", the Collattice logo, and "Collabot.dev" are trademarks of Bill Wheelock.

Breaking changes

This is a major release. The rename is the breaking change — functionality is otherwise unchanged.

• Webhook headers renamed. Deliveries now carry X-Collattice-Event, X-Collattice-Delivery-Id, and X-Collattice-Signature (User-Agent: Collattice-Webhooks). The old X-Collaboard-* headers are gone — there is no transition period where both are sent. Update any receiver that matches on header names when you upgrade.
• Release artifacts renamed. Downloads are now collattice-<platform> (e.g. collattice-win-x64.zip, collattice-linux-x64.tar.gz). Older releases keep their original names.
• Binaries and namespaces renamed. The server binary is now Collabot.Collattice.Api (.exe on Windows); .NET namespaces moved to Collabot.Collattice.*.
• Repository renamed. The source now lives at github.com/MrBildo/collattice. The old address redirects permanently — existing clones keep working.
• Browser preferences reset once. The web app's locally-stored preferences (theme, board view state) moved to new storage keys, so they reset one time on your first visit after upgrading.
• Fresh installations use Collattice-named locations. A brand-new install creates a Collattice folder and collattice.db database (see the install guide for per-platform paths).

Upgrading an existing installation

Nothing moves. The installer detects an existing Collaboard-era folder and database and leaves them exactly where they are — zero data movement, and your configuration is preserved through the settings merge. The full move to Collattice-named folders and a renamed database comes in a later release, with a tested, reversible migration procedure (already rehearsed end-to-end on a staging environment for this release).

The only action most operators need: re-point webhook receivers at the new header names.

What still says "Collaboard", and why

The rename is deliberately not a blind find-and-replace. What remains, and the plan for each:

Where	Why it stays for now	When it goes
Installer recognition of old install folders and collaboard.db (and the tests proving it)	So the installer can find an existing installation and protect its data	Removed with the future migration release
Install docs naming the old locations	So an upgrading user understands what was found and why their data stayed put	Same
Your existing data folder and database on disk	Renaming a live installation's data risks that data; this release refuses to	Migrated by the future migration release, using the rehearsed procedure
Old release downloads, tags, and commit history	Published history is permanent; rewriting it would break existing links and checksums	Never — history stands; everything from 3.0.0 forward uses the new name
The hosted demo hostnames	Changed on the hosting layer's own schedule so the running service is never interrupted	On the hosting schedule, shortly after this release
A handful of internal development-tool identifiers	Shared across several related projects; renamed together, on a coordinated schedule	With the coordinated internal-tooling update

Reliability and build hardening

The rename isn't the whole release — 3.0.0 also brings all the improvements since 2.1.0:

• Card-number allocation under heavily concurrent card creation is now retried more aggressively — measured to lose zero creations through 32-way concurrent bursts.
• Dependency updates clearing known advisories: axios 1.19.0, and react-router upgraded from the end-of-life v6 line to v7 (resolving three moderate advisories, with no application code changes); the bundled SQLite native library and OpenAPI libraries are now explicitly pinned.
• The bundled .NET runtime is pinned, with a CI gate that fails the build if it falls behind the current servicing release.
• Release archives are now verified against stray sourcemap references, and third-party attribution notices are regenerated and checked in CI.
• Webhook delivery tests and concurrency test fixtures were hardened, eliminating a class of intermittent CI failures.
• Published source comments were swept clean of internal work-tracking references — Collattice publishes its source, and the code now reads cleanly on its own for outside readers.