> ## Documentation Index
> Fetch the complete documentation index at: https://ayakaleaf-pro.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Ayakaleaf Pro v6.3.2 is released now

We are very proud to announce the release of Overleaf Pro 6.3.2. Upstream Overleaf 6.3.2 is a security release that updates Node.js, and we ship it together with a new member of the sync family: after GitHub, GitLab and Dropbox, your projects can now live in Gitea too.

### Changes

* Gitea Sync (early preview): two-way sync with gitea.com or your self-hosted Gitea.
* Node.js 24.22.1: the security update in upstream Overleaf 6.3.2.
* Bug fixes found by our E2E testing system and Internal Horizon Issue Investigation.

> [!NOTE]
>
> Gitea Sync ships in 6.3.2 as an **early preview** for gray testing, and will be officially released in v6.4.0. Its configuration and behavior may still change before then. It is off by default. Please report any issues on [GitHub](https://github.com/ayaka-notes/ayakaleaf-pro/issues).

#### Feature 01: Gitea Sync (Preview)

Many labs and small teams run their own Gitea, because it is light enough for a single small server. Gitea Sync works the same way as GitHub Sync and GitLab Sync: link your account, import a repository from the new project menu, or export a project to a new Gitea repository. Then push and pull from the editor, and merge through pull requests with the repository's own merge style. Overleaf never bypasses your branch protection: when a pull request needs approvals or passing checks, it waits for you to merge it in Gitea.

It works with gitea.com and with self-hosted Gitea 1.23 or later. Set `GITEA_SYNC_ENABLED`, `GITEA_SYNC_CLIENT_ID`, `GITEA_SYNC_CLIENT_SECRET` and `GITEA_TOKEN_CIPHER_PASSWORD`, plus `GITEA_SYNC_URL` for a self-hosted instance.

See [Gitea Synchronisation](https://ayakaleaf-pro.mintlify.site/on-premises/configuration/overleaf-toolkit/gitea-synchronisation.md "mention") for the full setup instructions.

#### Bug fixes

* **Git sync**: when a file deleted on GitHub, GitLab or Gitea cannot be deleted in Overleaf, the sync now fails and can be retried, instead of reporting success and leaving the file behind. A `git push` that deletes a file fails the same way.
* **Git bridge**: a document created in the editor with a non-text extension (such as `.csv`) stays editable when a `git push` changes it.
* **Track changes**: signed-out editors of a link-shared project can delete comment threads, but can no longer resolve or reopen them, and reviewers can delete their own replies.
* **Template gallery**: publishing a template requires access to the project.
* **Learn**: cached help pages stay available when the wiki cannot be reached.

See the [6.3.2 release notes](https://ayakaleaf-pro.mintlify.site/on-premises/release-notes/release-notes-6.x.x.md#ayakaleaf-pro-6.3.2 "mention") for the full list.

#### Upgrade

* From 6.3.1 or 6.3.0: no migration is needed. Pull the new image and restart.
* From 6.2.x or earlier with Zotero or Mendeley in use: run the [Zotero / Mendeley migration](https://ayakaleaf-pro.mintlify.site/on-premises/release-notes/release-notes-6.x.x.md#ayakaleaf-pro-6.3.0 "mention") from 6.3.0 first.
* Gitea Sync is off by default and only needs new environment variables.

#### Docker Image

You can find docker image here: [https://github.com/ayaka-notes/ayakaleaf-pro/pkgs/container/overleaf-pro](https://github.com/ayaka-notes/ayakaleaf-pro/pkgs/container/overleaf-pro)

```bash theme={null}
docker pull ghcr.io/ayaka-notes/overleaf-pro:6.3.2
```

***

> **Official Release Notes**
>
> **Release date:** 2026-10-23
>
> This is a security release containing updates to the installed packages.
>
> Source: [https://docs.overleaf.com/on-premises/release-notes/release-notes-6.x.x](https://docs.overleaf.com/on-premises/release-notes/release-notes-6.x.x)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.