Kamil Piechaczek

If the Commercial repository does not exist, the script does not crash, but prints a warning. This way, users can preview their changes. ``` yarn release:prepare-changelog --dry-run --date 2026-01-29 yarn...

I hope we will be able to remove the `resolutions` key, too: https://github.com/ckeditor/ckeditor5-react/blob/cdf5a75f9d6e2cc8f115cef7a67d5b59a1f53ec1/package.json#L77-L82

Could we verify if the issue is solved using the nightly builds?

Hi @rbalet, could you share steps to reproduce the issue? I'd like to understand the problem.

I'm sorry for not getting back to you sooner. I think the issue should be resolved in the latest release (https://github.com/ckeditor/ckeditor5-angular/releases/tag/v7.0.0). Could you guys confirm?

This issue is not related to the integration itself. Types from the `ckeditor5-watchdog` package imports things from `ckeditor5`. This leads to the conclusion that Watchdog should load `ckeditor5` as a...

_Internal conclusions:_ - Switch the current `@next` as `@latest`. - Update CKEditor 5 documentation to suggest using `v54` instead of `v43` when installing `ckeditor5-dev-*`. - We must check if [OIM...

@Witoso, there are also huge updates on the Node side. It understands imports between CJS and ESM packages, enabling a switch back to the _standard_ versioning model.

> [!IMPORTANT] > The project described below uses Node **v24.11.0**, which is the minimal required version for the `@ckeditor/ckeditor5-dev-*` packages. > > ```json > { > "engines": { > "node":...

While the issue has been closed automatically, I am processing the release of `ckeditor5-dev-*` right now.