Merge pull request #19764 from ckeditor/release_to_stable

Merge release (v47.5.0) to stable

Author: pomek

.circleci/config.yml

@@ -26,7 +26,7 @@ parameters:
     default: false
   chromeVersion:
     type: string
-    default: "143.0.7499.109"
+    default: "144.0.7559.59"
 
 orbs:
   continuation: circleci/continuation@0.1.2

.circleci/template.yml

@@ -108,7 +108,23 @@ jobs:
           command: |
             export PUPPETEER_EXECUTABLE_PATH="$(command -v google-chrome)"
             bash scripts/check-manual-tests.sh -r ckeditor5-root
-
+  
+  cke5_memory_leak_test:
+    docker:
+      - image: cimg/node:24.11.0-browsers
+    resource_class: medium
+    steps:
+      - checkout_command
+      - halt_if_short_flow
+      - browser-tools/install_chrome
+      - bootstrap_repository_command
+      - install_newest_emoji
+      - run:
+          name: Test for memory leaks
+          command: |
+            export PUPPETEER_EXECUTABLE_PATH="$(command -v google-chrome)"
+            pnpm run test:memory
+  
   cke5_validators:
     docker:
       - image: cimg/node:24.11.0
@@ -298,6 +314,11 @@ workflows:
             branches:
               ignore:
                 - stable
+      - cke5_memory_leak_test:
+          filters:
+            branches:
+              ignore:
+                - stable
       - release_prepare:
           filters:
             branches:
@@ -310,6 +331,7 @@ workflows:
             - cke5_coverage
             - cke5_validators
             - cke5_manual
+            - cke5_memory_leak_test
             - release_prepare
           filters:
             branches:
@@ -321,6 +343,7 @@ workflows:
             - cke5_tests_features_batch_n
             - cke5_validators
             - cke5_manual
+            - cke5_memory_leak_test
             - release_prepare
           filters:
             branches:
@@ -343,6 +366,7 @@ workflows:
       - cke5_tests_features_batch_n
       - cke5_validators
       - cke5_manual
+      - cke5_memory_leak_test
       - release_prepare
       - notify_ci_failure:
           hideAuthor: "true"

.gitignore

@@ -33,3 +33,10 @@ yalc.lock
 packages/*/src/**/*.d.ts
 packages/*/src/**/*.js
 packages/*/src/**/*.js.map
+
+# Memory leak test assets.
+scripts/memory/assets/*.js
+scripts/memory/assets/*.css
+
+# Ignore local environment variables.
+.env

CHANGELOG.md

@@ -0,0 +1,4 @@
+Software License Agreement
+==========================
+
+The license for this repository is maintained in [`packages/ckeditor5/LICENSE.md`](packages/ckeditor5/LICENSE.md).

LICENSE.md

@@ -3,7 +3,7 @@ category: features
 menu-title: Feature digest
 meta-title: Feature digest | CKEditor 5 Documentation
 meta-description: CKEditor 5 offers over 150 features, from basic editing capabilities like bold or italics to full-blown real-time collaboration - this page lists them all.
-modified_at: 2024-11-20
+modified_at: 2026-01-27
 order: -998
 ---
 
@@ -1168,17 +1168,71 @@ The Table of Contents feature is a dynamic tool for organizing documents. It all
 
 ## Productivity
 
-Speed up the content creation process with dedicated productivity utilities. The CKEditor AI feature brings generation, summarization, correction, contextual chat help, reviews, and many other capabilities right into the editor.
+Speed up the content creation process with dedicated productivity utilities. The CKEditor AI feature brings generation, summarization, correction, translation, contextual chat help, reviews, and many other capabilities right into the editor.
 
-<ck:heading-badge heading-id='ai-assistant' badge='premium'>CKEditor AI</ck:heading-badge>
+<ck:heading-badge heading-id='ckeditor-ai' badge='premium'>CKEditor AI</ck:heading-badge>
 
 By integrating AI writing assistance directly into the editing experience, CKEditor AI empowers authors with real-time AI writing support, streamlines content creation, and enhances editorial workflows across a wide range of use cases – from productivity boosts and proof-reading to content quality and consistency.
 
-<ck:button-link size='sm' variant='secondary' href='{@link features/ckeditor-ai-overview}'>
-	Feature page
-</ck:button-link>
+<ck:columns>
+	<ck:card>
+		<ck:card-title level='4' heading-id='ai-chat'>
+			AI Chat <ck:badge variant='premium' />
+		</ck:card-title>
+		<ck:card-description>
+			A conversational AI assistant that aids content creation and editing through a dynamic chat interface. It enables multi-turn interactions, context setting, model selection, and maintains chat history for quick reference.
+		</ck:card-description>
+		<ck:card-footer>
+			<ck:button-link size='sm' variant='secondary' href='{@link features/ckeditor-ai-chat}'>
+				Feature page
+			</ck:button-link>
+		</ck:card-footer>
+	</ck:card>
+
+	<ck:card>
+		<ck:card-title level='4' heading-id='ai-quick-actions'>
+			AI Quick Actions <ck:badge variant='premium' />
+		</ck:card-title>
+		<ck:card-description>
+			Streamline routine content transformations with one-click AI-powered suggestions directly within the editor. Choose from predefined commands or ask questions about selected text for instant AI insights.
+		</ck:card-description>
+		<ck:card-footer>
+			<ck:button-link size='sm' variant='secondary' href='{@link features/ckeditor-ai-actions}'>
+				Feature page
+			</ck:button-link>
+		</ck:card-footer>
+	</ck:card>
+
+	<ck:card>
+		<ck:card-title level='4' heading-id='ai-review'>
+			AI Review <ck:badge variant='premium' />
+		</ck:card-title>
+		<ck:card-description>
+			AI-powered quality assurance for content by running checks for grammar, style, tone, and more. Review and manage AI-suggested edits directly within the document to ensure content meets professional standards.
+		</ck:card-description>
+		<ck:card-footer>
+			<ck:button-link size='sm' variant='secondary' href='{@link features/ckeditor-ai-review}'>
+				Feature page
+			</ck:button-link>
+		</ck:card-footer>
+	</ck:card>
+
+	<ck:card>
+		<ck:card-title level='4' heading-id='ai-translate'>
+			AI Translate <ck:badge variant='premium' />
+		</ck:card-title>
+		<ck:card-description>
+			AI-powered translations with an intuitive interface for reviewing and managing translation suggestions directly within the document. Supports multiple languages with production-ready quality for common language pairs.
+		</ck:card-description>
+		<ck:card-footer>
+			<ck:button-link size='sm' variant='secondary' href='{@link features/ckeditor-ai-translate}'>
+				Feature page
+			</ck:button-link>
+		</ck:card-footer>
+	</ck:card>
+</ck:columns>
 
-<ck:heading-badge heading-id='ai-assistant' badge='premium'>AI Assistant (older version)</ck:heading-badge>
+<ck:heading-badge heading-id='ai-assistant' badge='premium'>AI Assistant (legacy)</ck:heading-badge>
 
 The AI Assistant feature enhances editing efficiency and creativity with artificial intelligence capabilities. It allows users to generate new content and process data through custom queries or utilize a set of predefined commands that are also customizable. The feature supports integration with multiple AI API providers: OpenAI, Azure OpenAI, and Amazon Bedrock. You can also integrate it with custom models.
 

docs/features/feature-digest.md

@@ -24,7 +24,7 @@ Each CKEditor 5 package has its own tests suite (see for example the [engin
 
 To run the automated tests, use the `pnpm run test [<args>...]` command.
 
-It accepts the following arguments that must be passed after the `--` option:
+It accepts the following arguments:
 
 * `--watch` (alias `-w`) &ndash; Whether to watch the files and execute tests whenever any file changes.
 * `--source-map` (alias `-s`) &ndash; Whether to generate useful source maps for the code.
@@ -205,6 +205,53 @@ pnpm run manual:verify
 
 Read more about the crawler in the {@link framework/contributing/development-environment#verifying-documentation Verifying documentation} guide.
 
+## Running memory leak tests
+
+To run the memory leak tests, use the `pnpm run test:memory` command. It builds a browser bundle, starts a local server, and runs the tests in headless Chromium.
+
+The command accepts the following arguments:
+
+* `--editor` &ndash; A list of editor names to test. You can pass the option multiple times. Defaults to `BalloonEditor`, `ClassicEditor`, `DecoupledEditor`, `InlineEditor`, and `MultiRootEditor`.
+* `--html` &ndash; The HTML file to load from `scripts/memory/assets`. Defaults to `index.html`.
+* `--no-build` &ndash; Skips generating the browser build and reuses the existing editor assets.
+
+### Examples
+
+Run all memory leak tests:
+
+```
+pnpm run test:memory
+```
+
+Test only the classic and inline editors:
+
+```
+pnpm run test:memory --editor ClassicEditor --editor InlineEditor
+```
+
+Use a custom HTML file from `scripts/memory/assets`:
+
+```
+pnpm run test:memory --html my-test.html
+```
+
+Reuse existing assets:
+
+```
+pnpm run test:memory --no-build
+```
+
+### Interpreting the results
+
+Each editor run consists of multiple create/destroy cycles. The warmup phase creates and destroys the editor a few times to populate caches and JIT state. The actual test then repeats the same create/destroy cycle more times while sampling memory between cycles. This makes the results less sensitive to first‑run effects and helps highlight steady growth trends.
+
+After the run completes, the summary table reports:
+
+* **Baseline** &ndash; The memory level after warmup. It is the reference point for the rest of the run and should already include initial cache effects.
+* **Growth** &ndash; The difference between the final measurement and the baseline across repeated cycles. Use this to spot steady memory increases over time rather than one‑off spikes.
+* **Tail Growth** &ndash; The spread within the last few measurements. It helps verify that memory stabilized near the end; large values suggest a still-growing footprint or high noise even after multiple cycles.
+* **Status** &ndash; `OK` when both Growth and Tail Growth stay below the threshold. `Exceeds threshold` or `Error` means the run should be treated as a failure.
+
 ## Rules for using the `--files` option
 
 The `--files` (alias `-f`) option is used by both the manual and automated tests. Running tests for the root of the mono-repository is no longer supported. Each set of tests should be assigned to a package, and placed in `tests` directory. It accepts the following types of patterns: