CKEditor 5 v46.1.1 & v46.1.0 Release Highlights: Infrastructure Updates, Targeted Fixes, and UX Improvements
The CKEditor 5 v46.1.1 release, published on 15 September 2025, focuses on our development infrastructure and release process. These changes ensure greater stability, efficiency, and long-term maintainability of the editor.
Additionally, 10 September 2025 marked the release of CKEditor 5 v46.1.0, which delivered a set of targeted fixes and usability improvements.
Together, these two updates strengthen both the internal foundation of CKEditor and the day-to-day editing experience. You can refer to the changelog for full details.
Development Infrastructure
The v46.1.1 release does not introduce changes to the editor’s API or features. Instead, it delivers fully backward-compatible improvements to our development environment and release process, strengthening stability and efficiency. These updates include:
-
Migration from Yarn Classic to pnpm for faster installation, better peer dependency handling, and disk usage efficiency.
-
Introduction of dependency locking mechanisms to ensure consistent, reproducible build environments across development setups and CI/CD pipelines.
If you fork the repository and work directly with the source code, make sure to update your development setup following our development environment guide.
Other Updates and Improvements
The v46.1.0 release delivered multiple improvements that enhance stability and user experience. These updates include:
-
Pagination: Stability fixes, especially in scenarios with long tables.
-
Server-side Editor API: Introduced a
hidden_in_presence_listflag to prevent automation script accounts from appearing in presence lists. -
Comments: Automatic removal of markers pointing to non-existing comment threads.
-
Drag & drop on iOS: A smoother and more reliable widget dragging experience on touch devices.
The v46.1.0 release also introduced a minor breaking change. The CloudServicesCommentsAdapter#getCommentThread no longer throws an error when a thread does not exist. It now returns null.
