Release Notes

See Versions for how to get more detailed information. This page mentions more high-level releases, changes, etc.

4.2.2 (2026-05-04): Conat client reconnect fix

Bugfix release for the Conat subscription resync after a hub reconnect: long-lived clients could silently lose subscriptions, leaving the connection healthy-looking but operations timing out (upstream PR). Hub, project-server, and the static frontend are all rebuilt because they share the same conat client. Existing project pods keep their old project-server until next restart, so the fix lands gradually.

4.2.1 (2026-05-04): Per-project PVC mode bugfix

Bugfix release for per-project PVC mode (introduced in 4.2.0): cross-project file copy and the public share publisher now work in this mode. manage drives rsync over SSH to port 2222 of the project pod, reusing the ssh-gateway keypair. The chart wires up the required mounts, NetworkPolicy, and RBAC automatically when manage.perProjectPVC is enabled, and fails fast if the mode is configured without global.ssh_gateway.enabled: true.

Warning

4.2.0 is marked defective for deployments running per-project PVC mode. The shared-PVC default is unaffected.

4.2.0 (2026-04-29): Updates to All Core Components

Updates to all core components (hub, manage, static, project server) with upstream improvements and bugfixes.

New features in this release:

  • Per-project PVC mode (advanced, optional): the manage service can create one PersistentVolumeClaim per project instead of using a shared PVC with sub-paths. Useful for ReadWriteOnce-only storage classes (Longhorn, EBS, Ceph RBD), per-project storage quotas, and per-project snapshots. See Per-project PVC mode (advanced) and Per-project PVC mode.

  • Faster S3 mounts via geesefs: the datastore sidecar now ships with geesefs as the default fuse client for type=s3 mounts (faster on large files and honors the region field). The legacy s3fs backend remains available for fallback. Selection is deployment-wide via manage.datastore.s3Backend and per-mount via the mount’s JSON config — see S3 fuse backend.

  • Minimal Jupyter image: a new lean Jupyter project image is available alongside the existing tiers, for deployments that need a smaller-footprint kernel environment. See the announcement.

  • Anchored chats in Jupyter and LaTeX: chat threads can now be anchored to a specific cell or location in a Jupyter notebook or LaTeX document, keeping the conversation tied to the content it discusses. See the announcement.

4.1.0 (2026-01-27): Major Bugfixes and Feature Updates

This release focuses on stability, robustness, and key new features:

  • Major bugfixes addressing stability issues and memory leaks across all components

  • Exclusive SSO support via catchall domain configuration using ["*"] - enables mandatory SSO for all users

  • New LaTeX editor with improved user interface and editing experience

  • General robustness improvements and performance optimizations

4.0.0 (2025-07-10): The “Conat” update

Warning

This is a breaking change, so you need to upgrade all components of CoCalc at the same time. You also have to delete all project pods after this upgrade. It’s also not backwards compatible with previous versions.

Conat is a new internal communication architecture for distributed applications. This is a major change of the inner workings of CoCalc, but it should not affect users in any way. If at all, everything should be faster and more reliable.

3.7.1 (2025-01-31): MIG GPU Support

See https://github.com/sagemathinc/cocalc/issues/8161 for GPU Support.

3.6.0 (2024-12-09): SSO and Software Environment

New default software environment (SageMath 10.5 and other updates) and updating known working versions of dependencies.

Also, improving documentation for configuring Single Sign On, configuring a Software Environments and building a Custom Software Environment.

3.5.0 (2024-10-07): New file watcher

Projects (project server) now use a new file-watcher to detect changes to files. This should be more robust across various types of file-systems.

3.4.0 (2024-08-30): Ubuntu 24.04

Images are now based on Ubuntu 24.04, which refreshes the available software, etc.

3.3.0 (2024-07-31): Support multiple instances

On Kubernetes’ side, non-namespaced resources now get a unique name. This makes it easier to deploy multiple instances in the same cluster across different namespaces.

3.1.0 (2024-06-17): GPU Support via Licenses

Simplifies configuring specific projects to make use of a GPU: GPU Support.

3.0.0 (2024-05-20): Splitting Project Server vs. Software Environment

From now on it is much easier to create customized software environments, because there are only very minimal requirements on the software image you have to provide.

2.16.0 (2024-05-08): static service

Breaking change: The Static service does not need a ClusterIP and we set it to None – for consistency with the other services.

This will cause a conflict when Updating via HELM. Simply delete the service before upgrading will fix this:

$ kubectl [--namespace cocalc] delete service static

2.15.0 (2024-04-11): Sage 10.3, more LLMs, etc.

This makes more language models available, updates Sage to 10.3, and various bugfixes.