What's Changed

• Fix workspace create account context by @hakanshehu in #294
• Fix cleanup on account logout by @hakanshehu in #296

Full Changelog: v0.4.2...v0.4.3

What's Changed

• Fix otp code expiresAt parsing by @hakanshehu in #292
• Fix scroll in node modal by @hakanshehu in #293

Full Changelog: v0.4.1...v0.4.2

What's Changed

• Bump Valkey chart dependency to 5.1.0 by @ylber-gashi in #288
• Remove content type parsers to handle empty JSON body errors by @hakanshehu in #289
• Add tryDeleteFile utility for safe file deletion in file-upload-tus.ts by @hakanshehu in #290
• Allow decimal values in number field by @hakanshehu in #291

Full Changelog: v0.4.0...v0.4.1

We're excited to announce Colanode v0.4.0, a significant release that brings major improvements to both the server and client applications. This release focuses on simplifying server configuration, improving client-side navigation, and enhancing the overall user experience.

Important: This release contains breaking changes. We recommend all self-hosters read through this post and the self-hosting documentation before upgrading. Client apps will reset local data after upgrading, requiring users to log in again and sync from the beginning.

Server Changes

JSON-Based Configuration

The most significant server-side change is how Colanode handles configuration. Previously, everything was managed through environment variables. As our configuration options grew, this approach became unwieldy and hard to maintain.

We've moved to a JSON-based configuration system where config.json is the primary source of truth. This gives you much more flexibility and clarity when configuring your Colanode server.

Here's how the new system works:

1. Sensible defaults are built-in. The server runs with reasonable defaults out of the box. You only need a custom config.json when you want to change specific settings.

2. Override with a config file. Set the CONFIG environment variable to point to your JSON file. The file only needs to contain the fields you want to override.

3. Secrets stay in env vars. Reference secrets in your config with env://VAR_NAME. At runtime, the loader resolves those pointers from the process environment.

4. File contents support. You can inline file contents (like certificates) using file://path/to/file.

For example, here's a configuration snippet showing how to set up S3 storage with secrets referenced from environment variables:

{
  "name": "My Company Colanode",
  "storage": {
    "provider": {
      "type": "s3",
      "endpoint": "http://minio:9000",
      "bucket": "colanode",
      "region": "us-east-1",
      "forcePathStyle": true,
      "accessKey": "env://S3_ACCESS_KEY",
      "secretKey": "env://S3_SECRET_KEY"
    }
  }
}

The only required environment variables are POSTGRES_URL and REDIS_URL, since the default config references them. Everything else can be configured in the JSON file.

For Docker Compose deployments, create a config.json, mount it as a volume, and set CONFIG=/config.json in your environment block. For Kubernetes, enable colanode.configFile.enabled in your Helm values.

Check out the full configuration reference for all available options.

Simplified Storage Limits

We've simplified how storage limits work. Previously, we used a combination of database triggers and aggregations in a counters table to track storage usage. This approach was getting complex and error-prone, especially for self-hosters making customizations.

In this release, we've removed the total storage tracking for users and workspaces. We now only enforce the maxFileSize limit at the workspace level, which controls the maximum size of individual file uploads (default: 500 MB).

This change keeps the open-source codebase cleaner and easier to maintain. We plan to implement a more robust limits and restrictions system when we introduce AI features.

Workspace Read-Only Mode

We've introduced a read-only mode for workspaces. This is useful when you want to restrict all data changes while still allowing users to read content.

When a workspace is in read-only mode:

• All node and document updates are blocked
• File uploads are blocked
• Users can still read and navigate all content

To enable read-only mode, set the status column to 2 in the workspaces table in your PostgreSQL database.

Client Changes

URL-Based Routing with TanStack Router

We've integrated TanStack Router across both web and desktop applications. This brings several improvements:

• Shareable URLs: The URL in the web app now represents the current node you're viewing. You can share this URL with other workspace members, and they'll navigate directly to that content.
• Browser navigation: Use your browser's back and forward buttons to navigate through your history.
• Deep linking: Bookmark specific pages, records, or folders and return to them instantly.

Redesigned Tabs

We've rethought how tabs work based on user feedback:

• Web app: Tabs have been removed. Since browsers already have their own tab system, having a second layer of tabs was causing confusion. The new URL-based routing makes it easy to open multiple nodes in separate browser tabs.

• Desktop app: Tabs are now at the app level instead of the workspace level. This means you can have tabs open across different workspaces, making it easier to work with multiple contexts simultaneously.

TanStack-db for Local State

We've adopted TanStack-db for managing local state and reactivity. This brings significant improvements:

• Faster loading: Data loads even faster than before.
• Instant feedback: Most changes you make now appear instantly thanks to optimistic mutations.
• No more flickering: We've eliminated the occasional "flicker" effects some users experienced when data was updating.
• More stable reads: Combined with our local-first sync engine, data changes and reads are now more reliable and consistent.

Quick Preview Modals

You can now preview files and records in a modal directly from database views or folders. This is great for quickly checking content without leaving your current context. Of course, you can still open any record as a full page when you need the complete view.

Database Locks

A highly requested feature: you can now lock database fields and views. This prevents accidental changes or deletions, which was a pain point for some users who accidentally deleted important fields.

Node Tree View in Sidebar

The sidebar now shows a tree view of child nodes for pages and databases, not just spaces. This makes it much easier to navigate deeply nested content without opening each node individually.

Note: We've temporarily disabled drag-and-drop reordering of nodes in the sidebar. The previous implementation had some edge cases that weren't handled well. We'll re-enable this feature in a future release once we've addressed those issues.

Other Client Improvements

• Improved authentication flow: We've redesigned the auth screens and improved the overall authentication experience.
• Better server management: Servers are now displayed more clearly in the UI. Self-hosted web apps no longer automatically add Colanode Cloud. Servers that aren't actively used now sync much less frequently (instead of every minute), reducing unnecessary network traffic.

Bug Fixes

Alongside these major changes, we've fixed numerous bugs:

• Fixed calendar view filtering issues
• Number fields now properly allow decimal values
• Various UI fixes for dialogs
• Form component refactoring and improvements

Upgrading

For self-hosters:

1. Review the new configuration documentation
2. Create a config.json if you need custom settings
3. Update your deployment to use the new configuration system
4. Upgrade your server to v0.4.0

For all users:

• After upgrading the client app, you'll need to log in again
• All local data will be synced fresh from the server

If you encounter any issues during the upgrade or while using the new version, please open an issue on GitHub or contact us through our contact form.

What's Changed

• Fix node22 lightningcss workaround by @eljonny in #231
• Implement new routing with tanstack router and mobile app kickoff by @hakanshehu in #248
• Improve breadcrumbs, headers and tabs by @hakanshehu in #249
• chore: fix npm security vulnerabilities by @AlexandreGoumain in #250
• Improve authentication flow by @hakanshehu in #251
• Add animation for login screen and improve app loading screen by @hakanshehu in #252
• Improve server loading and syncing by @hakanshehu in #253
• Increase sync batch size by @hakanshehu in #257
• Improve storage tracking and UI by @hakanshehu in #259
• Fix calendar view filtering by @hakanshehu in #260
• Open records in a modal by @hakanshehu in #261
• Fix query subscription in web by @hakanshehu in #262
• Open in modal and other file improvements by @hakanshehu in #263
• Introduce config.json-driven server config by @ylber-gashi in #246
• Update packages by @hakanshehu in #267
• Use tanstackdb for queries and mutations by @hakanshehu in #275
• Remove debug configuration section from config.json by @ylber-gashi in #271
• Refactor forms with tanstack-form by @hakanshehu in #276
• fix calendar view day component to use td for proper table structure by @hakanshehu in #277
• Update pakcages by @hakanshehu in #278
• Implement database locks by @hakanshehu in https://github.com...

What's Changed

• Implement a cleanup job for deleting orphan data by @hakanshehu in #242
• Fix date picker date conversion by @hakanshehu in #243
• Add Colanode Cloud plan upgrade card by @hakanshehu in #244

Full Changelog: v0.3.10...v0.3.11

What's Changed

• Add configurable storage backends (File, S3, GCS, Azure) by @ylber-gashi in #225
• Fix editor toolbar menu rendering by @hakanshehu in #232
• Update packages by @hakanshehu in #233

Full Changelog: v0.3.9...v0.3.10

What's Changed

• Improve sleep scheduler implementation for jobs by @hakanshehu in #223
• Update packages by @hakanshehu in #224

Full Changelog: v0.3.8...v0.3.9

What's Changed

• Fix MacOS title dots placeholder by @hakanshehu in #219
• Use new logo for assets by @hakanshehu in #220

Full Changelog: v0.3.7...v0.3.8

What's Changed

• Fix message files handling by @hakanshehu in #210
• Add a message in file preview if it hasn't been uploaded yet by @hakanshehu in #211
• Update packages by @hakanshehu in #212
• Improve file preview handling for non finished uploads by @hakanshehu in #213
• Consider servers as available by default on init by @hakanshehu in #214

Full Changelog: v0.3.6...v0.3.7

What's Changed

• Fix issues with ArrayBuffer compatibility by @eljonny in #204
• Fix onClick and floating mounting for slash command menu in editor by @hakanshehu in #205
• Fix onClick and floating mounting for mention menu by @hakanshehu in #206

Full Changelog: v0.3.5...v0.3.6