Tangled moves collaboration history beside the repository
Tangled’s code-forge redesign stores issues, pull requests, comments and labels as Git objects beside repository code on its hosting server. User attestations on AT Protocol identify the exact record versions they authored. The release also replaces its central Go web application with a Svelte frontend and distributed in-memory Rust indexers, separating portable repository history from the services that display it.
Tangled · Oct 30, 2026
Why it matters
A project’s review discussions and issue history need a migration path as much as its Git commits do.
More context
The October 30 release includes organizations and stacked pull requests. Existing self-hosters must follow the knot v1.20.0 upgrade guide, including required contact and storage settings. Start with a test repository or review that migration before moving active collaboration.
Keep in mind
The launch is staged: private repositories, a CLI and SDKs are described as upcoming. Federation and signed records do not remove operational duties; the announcement is not an independent availability or performance evaluation.
Original read